We want to use `oc apply` with a SCC whose `volumes` field is not alphabetically sorted. While applying the SCC, the `volumes` field gets auto-sorted (and appears as such in the SCC and last-applied-configuration annotation).

As a result, when we run `oc apply` again with the same file, it notices that the `volumes` arrays are different (the one from the file is not sorted, the one in the cluster is sorted) and re-applies the file as if it was modified, i.e. it behaves as if it performed a modification on the file but doesn't.
   
This will be better explained with a example in comments.

This has been reproduced in 4.12.36 and 4.16.2

Always

    1. Use oc apply to create a SCC that has a volumes field that is NOT sorted alphabetically
    2. Run oc apply to the same file after creation many times
    3.

oc apply behaves as if it made a change, outputting that the resource has been "configured" and increasing the resourceVersion

oc apply to properly detect that no change is required. Output that the resource is "unchanged". No increase in resourceVersion.

In internal comments (both examples and impact).