Automation process to handle issue transfers between opensearch-project repos.

[prudhvigodithi]

Is your feature request related to a problem? Please describe

Need an automation process to handle transferring of issues between repos. Right now its manual and user tags @opensearch-project/admin group to do the issue transfer, example https://github.com/opensearch-project/security-analytics-dashboards-plugin/issues/964, https://github.com/opensearch-project/observability/issues/1808#issuecomment-1979370370, https://github.com/opensearch-project/dashboards-observability/issues/1483#issuecomment-1979080660 and someone from @opensearch-project/admin do it manually.

Acceptance Criteria

A very high level process using GitHub App and can be improved based on feedback.

• Start by creating a generic infra GitHub App (this can be extended for other automations in future).
• Add a issueTransfer class for this app that can take care of transferring the issue
• Add a label transfer.
• GitHub App should respond to this label action (Only maintainers have access to change/add labels per github).
• The github app should be generic for multiple purposes.
• Looks for the comment from maintainers that has the destination repo.
• If no comment then GitHub App should be add a comment as label transfer added but not provided any destination repo.
• Transfer the issue.
• If failed add a comment as failed transferring with an error message and then tagging @opensearch-project/admin group.
• Needs SOP to help maintainers to understand the process.

Describe alternatives you've considered

No response

Additional context

No response

[peterzhuamazon]

More exit criteria needs to added with different options, due to this can cause a lot of github API calls by the bot.

[peterzhuamazon]

Similar to https://github.com/opensearch-project/opensearch-build/issues/4455 on the fundamental of github app. Add together.

[peterzhuamazon]

App creation requested.

[peterzhuamazon]

Test code in progress with probot now.