feat: Dynamic repo registration

[egekocabas]

Warning

❗ ❗ ❗ This PR contains a migration script ❗ ❗ ❗

Motivation

Enable dynamic repository syncing by accurately tracking which repositories have the GitHub App installed. This ensures our system reflects real-time changes when repositories are added or removed.

Description

• Webhook Listener Refactoring
  • Updated GitHubCustomMessageHandler to deserialize events and delegate processing to extenders, following the org.kohsuke:github-api library implementation that we have.
  • Introduced isGlobalEvent() in both GitHubCustomMessageHandler and GitHubMessageHandler to differentiate global events (like installation_repositories) from repository-specific ones.
• Subscription to global events
  • Modified NatsConsumerService.getSubjects to correctly subscribe to global events using the pattern github.?.?.installation_repositories.
• Repository Sync Foundation
  • Updated GitHubFacade to fetch the list of repositories where the GitHub App is installed.
    • If the auth type is PAT, then it returns repositories defined in the environment variable.
• GitHubDataSyncService Refactoring
  • Refactored the service to sync individual repositories using the repository name with owner.
  • Added repositoryNameWithOwner and status columns to DataSyncStatus to maintain dedicated sync records.
  • Did not added cascade deletion for DataSyncStatus since the repository record isn’t available during the initial sync. Also it is not that important for DataSyncStatus.
  • Didn't make it @Async since it was causing so much errors related with User table. Further refactoring and making 'data syncing' async can be achieved if we add repository_id column to User table.
• SyncService Class Updates
  • Moved all the methods except the process methods to a new class called GitHubDataSyncOrchestrator. This change was necessary since we used to call these individual process methods inside it's own bean (SyncService) but this was causing self-invocation for the @Transactional annotation.
• GitHubInstallationRepositoriesMessageHandler
  • Event listener for GitHub App installed / removed to a repository events.
  • Whenever a repository removed the GitHub App, then we remove its data from db.
  • Whenever a repository adds the GitHub App, then we start data sync for that repository.
  • At the end of this event handler, we update the subjects we listen from NATS.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 088d91f1	✅ 0.00%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (088d91f)	Report Missing	Report Missing	Report Missing
Head commit (f68172c)	4844	326	6.73%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#351)	517	0	0.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[TurkerKoc]

Thanks for this important update! Now it's extremely easy for anyone in ls1intum to install our Github App and start using Helios!

We did a testings session with @egekocabas and tried locally installing/removing our dummy Github App into our dummy repo. It works like a charm 🚀

Besides some minor issues we've talked, code also looks fantastic. Let's address them.

Also it would be great if we can add some documentation to guide repository owners to setup their repo in Helios. Here is a discussion for that.
Please also do not forget to mention how they should setup their deployment workflow!

Thanks for the efforts!

[TurkerKoc]

Great Job! Thanks for addressing al the points we've discussed 🚀