Implement Repository Removal Synchronization between Backstage and GitHub

[maxmurphySF]

Current Issue:

• Currently, when users create a repository in Backstage, it automatically creates a corresponding repository in GitHub.
• However, when users remove a repository within Backstage, the associated GitHub repository is not removed, leading to confusion and potential inconsistencies.
• This mismatch between Backstage and GitHub repository states can cause issues, such as orphaned repositories, redundant data, and difficulties in managing the overall repository lifecycle.

Remediation:

• Implement a synchronization mechanism between Backstage and GitHub to ensure that repository removal actions are propagated consistently across both platforms.
• When a user removes a repository from Backstage, the system should automatically detect the associated GitHub repository and initiate the removal process on GitHub as well.
• Appropriate checks and validations should be in place to ensure that only authorized users can perform repository removal actions, both in Backstage and on GitHub.
• Provide clear notifications and confirmations to users before removing repositories, ensuring that accidental deletions are minimized.
• Implement error handling and logging mechanisms to track any issues or failures that occur during the repository removal synchronization process.

[sadarunnisa-sf]

Removal of repository as per UN-registering entity won't be possible. As entities could be components, apps repo, data pipeline or services. So its just not repos which we consider entity in backstage but more than that