chore: add script for auto-assignement of RFH issues

What does this MR do?

This MR adds script to automate assignment of RFH issues. The algorithm is as follows:

Issue Count Determination and Assignment Algorithm

Current Issue Counts

The script determines current issue counts through a three-tier classification system:

• Unassigned Issues: Issues without any assignees and not in "closed" state are collected for assignment
• Team-Assigned Issues: Issues directly assigned to team members (from the team_members list) increment that member's count
• Bot-Triaged Issues: Issues assigned to non-team members are checked for automation bot processing:
  • The script searches issue comments for SISSUE_AUTOMATION_TAGS pattern
  • If found with valid ASSIGNED_TO:username tag, it counts toward that team member's workload
  • This captures issues that were triaged by the team but forwarded to other users
• Ignored Issues: Issues manually assigned to non-team members without bot processing are excluded from counts
• script is configured to look back 90 days when calculating counts

Assignment Algorithm

For unassigned issues, the script uses a load-balanced random assignment approach:

• Identifies team member(s) with the minimum current issue count
• If multiple members tie for minimum count, randomly selects one from the candidates
• Assigns the issue to the selected user via GitLab API
• Increments that member's count
• Adds a comment with automation tags (ASSIGNED_TO:username) for future tracking
• Repeats for each unassigned issue

This ensures work is distributed evenly while maintaining some randomness when workloads are equal.

I have created and stored a GL access token for this script with api scope and developer access.

Related to #1733 (closed)

Author checklist

• Assign one of conventional-commit prefixes to the MR.
  • fix: Indicates a bug fix, triggers a patch release.
  • feat: Signals the introduction of a new feature, triggers a minor release.
  • perf: Focuses on performance improvements that don't introduce new features or fix bugs, triggers a patch release.
  • docs: Updates or changes to documentation. Does not trigger a release.
  • style: Changes that do not affect the code's functionality. Does not trigger a release.
  • refactor: Modifications to the code that do not fix bugs or add features but improve code structure or readability. Does not trigger a release.
  • test: Changes related to adding or modifying tests. Does not trigger a release.
  • chore: Routine tasks that don't affect the application, such as updating build processes, package manager configs, etc. Does not trigger a release.
  • build: Changes that affect the build system or external dependencies. May trigger a release.
  • ci: Modifications to continuous integration configuration files and scripts. Does not trigger a release.
  • revert: Reverts a previous commit. It could result in a patch, minor, or major release.
• MR contains database changes including schema/background migrations:
  • Do not include code that depends on the schema migrations in the same commit. Split the MR into two or more.
  • Do not include code that depends on background migrations in the same release.
  • Manually run up and down migrations in a postgres.ai production database clone and add a link for the query plan(s) to the MR.
  • If adding new schema migrations make sure the REGISTRY_SELF_MANAGED_RELEASE_VERSION CI variable in migrate.yml is pointing to the latest GitLab self-managed released registry version. Find the correct registry version here. Make sure to select the branch of the latest GitLab release.
  • If adding new queries, extract a query plan from postgres.ai and post the link here. If changing existing queries, also extract a query plan for the current version for comparison.
    • I do not have access to postgres.ai and have made a comment on this MR asking for these to be run on my behalf.
  • If adding new background migration, follow the guide for performance testing new background migrations and add a report/summary to the MR with your analysis.
• Change contains a breaking change - apply the breaking change label.
• Change is considered high risk - apply the label high-risk-change
• I created or linked to an existing issue for every added or updated TODO, BUG, FIXME or OPTIMIZE prefixed comment
• Changes cannot be rolled back
  • Apply the label cannot-rollback.
  • Add a section to the MR description that includes the following details:
    • The reasoning behind why a release containing the presented MR can not be rolled back (e.g. schema migrations or changes to the FS structure)
    • Detailed steps to revert/disable a feature introduced by the same change where a migration cannot be rolled back. (note: ideally MRs containing schema migrations should not contain feature changes.)
    • Ensure this MR does not add code that depends on these changes that cannot be rolled back.

Documentation/resources

Code review guidelines

Go Style guidelines

Feature flags

When documentation is required

Documentation workflow

Reviewer checklist

• Ensure the commit and MR tittle are still accurate.
• If the change contains a breaking change, verify the breaking change label.
• If the change is considered high risk, verify the label high-risk-change
• Identify if the change can be rolled back safely. (note: all other reasons for not being able to rollback will be sufficiently captured by major version changes).