Replace use of `MoJ Bot` token in `ministryofjustice/github-collaborators` (OPS_BOT_TOKEN)

[tamsinforbes]

User Need

As a member of the operations engineering team, I want to organise and secure the GitHub personal access tokens in the moj-operations-engineering-bot account, so that we can reduce risks, improve clarity, and align with best practices in token management.

Value

Properly managing these tokens will significantly reduce security risks by limiting their scope and improving their traceability. It will also streamline our processes by creating a clear and efficient method for future token creation and management.

MoJ Bot Classic token currently used in ministryofjustice/github-collaborators as GitHub secret OPS_BOT_TOKEN.

Functional Requirements:

• [x] Create new token for use in ministryofjustice/github-collaborators as per standards agreed in ADR 020

Acceptance Criteria:

• [x] See here for proposed new token and GitHub Secret name
• [x] New token name, description, scope, permissions etc adhere to ADR 020
• [x] The OPS_BOT_TOKEN GitHub secret in ministryofjustice/github-collaborators is renamed and updated to use the new token.
• [x] Checked it works
• [x] Deleted superfluous GH secret
• [x] Checked it still works!

[tamsinforbes]

created token MOJ_COLLABORATORS_GENERAL_ADMIN in bot account

MOJ_COLLABORATORS_GENERAL_ADMIN FG-PAT as GitHub Secret MOJ_COLLABORATORS_GENERAL_ADMIN_BOT_PAT

Permissions scope - all repos Repo perms: Admin RW; PR RW; Issue RW; Contents RW; Webhooks RW; Org perms; Admin RW; Member R