accesscontextmanager - Update ingress / egress array ordering semantics

[Charlesleonius]

Fixes a permadiff in ingress / egress fine grained resources in cases where the API returns a different ordering for lists.

accesscontextmanager: fixed a permadiff in ingress / egress fine grained resources in cases where the API returns a different ordering for lists

[github-actions]

Hello! I am a robot. Tests will require approval from a repository maintainer to run.

@trodge, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look.

You can help make sure that review is quick by doing a self-review and by running impacted tests locally.

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR hasn't generated any diffs, but I'll let you know if a future commit does.

[trodge]

This field doesn't seem to have any effect on the generated code. Was the intention to make these fields into sets? If so, that may be a breaking change.

[github-actions]

@trodge This PR has been waiting for review for 3 weekdays. Please take a look! Use the label disable-review-reminders to disable these notifications.

[Charlesleonius]

@trodge I was under the impression that we could ignore the ordering of fields without making them sets to avoid a breaking change but that only works for top level fields. Im looking for other work arounds because this is causing a permadiff and waiting till the next major release is not an option for some customers