Create new BCROS staff account for BCOL Help Desk.

> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2024-01-30. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMjA4NTcy)._

Currently there are 2 staff account types in BCROS, 1 used for BC Registries, BCOL Admin, BCOL help desk staff and one for SBC Service agents . All staff have for the most part the same access when in fact not all staff require this access.

Due to the recent announcements regarding the organization, other areas maybe added to this acct., ie. IDIM, BCOL Admin. recommend to create new GOVM acct with read only.

Plan from Nov 5th 2024:
1. A new GOVM account will be created for this team (Varek to confirm future name)
2. A new KeyCloak group will be created that bundles existing staff roles
3. Ops will handle adding/removing this group to the team members. (OCM needed to explain this to BCOL HD team lead)
4. Analysis task to describe which access is possible per partner application (e.g. what about Business Filings?)

No repository files, tests, or entry points are named. Start by reviewing the planned GOVM account and KeyCloak group with the BCOL Help Desk team, then document access possibilities for each partner application; done means the account, bundled roles, ownership process, and access analysis are agreed.

Written by the indexing model from the issue text.