[PM-2102] Fix broken access selector component

[shane-melton]

Type of change

- [X] Bug fix
- [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

Implement logic to keep row control enable/disable status in sync with the access item properties whenever the parent form group in the access selector is enabled/disabled.

Angular 15 introduced a breaking change that calls setDisabledState() whenever a CVA is added. While not a problem on its own, it did reveal a flaw in how the access selector component would enable/disable its internal form group. When the setDisabledState() is called it calls enable() on the internal form group, which cascades to all of the child controls; effectively re-enabling all the internal form group rows (even those that should have remained disabled due to their read only status).

Fixes #5328

Code changes

• apps/web/src/app/admin-console/organizations/shared/components/access-selector/access-selector.component.ts: Add the logic explained above
• libs/angular/src/utils/form-selection-list.ts: Add helper method to easily iterate over a FormSelectionLists controls and values

Before you submit

• Please add unit tests where it makes sense to do so (encouraged but not required)
• If this change requires a documentation update - notify the documentation team
• If this change has particular deployment requirements - notify the DevOps team
• Ensure that all UI additions follow WCAG AA requirements