Rebrand Codebase from Sentry Software to MetricsHub

[ChristopheClermont]

Issue: Rebrand Codebase from Sentry Software to MetricsHub

Description
Following the organization change from Sentry Software to MetricsHub, the codebase needs to be updated to reflect the new naming convention. This includes adjusting package names, imports, and Maven configurations.

Tasks

• Update the pom.xml files:
  • Change groupId from org.sentrysoftware to org.metricshub.
  • Change the artifactId accordingly to repository name (lowercase) tablejoin.
  • Update the parent dependency to latest MetricsHub OSS Parent available.
  • Ensure artifact coordinates reflect the new organization.
  • Update the Organization to MetricsHub
• Update all Java package names from org.sentrysoftware to org.metricshub.
• Rename corresponding directories to match the new package structure.
• Adjust all import statements to reflect the new package names.
• Review and update any documentation mentioning Sentry Software (README, Javadoc, comments, etc.).
• Verify that the build and tests pass after these modifications.

Additional Notes

• Ensure that any references in CI/CD configurations (GitHub Actions, Jenkins, etc.) are updated accordingly.
  • Change the .github/workflows files to redirect to MetricsHub workflows
• If publishing artifacts to a repository (e.g., Maven Central, internal Nexus), verify that the updated coordinates comply with publishing requirements.

Impact
This rebranding ensures that all future developments align with MetricsHub's structure, avoiding inconsistencies and potential conflicts in dependencies.