SCRUM-3693: roll down MaTI DB between environments

[abecerra]

• Fix the integration tests failure (SCRUM-3692) imposing ordering and making the GET counters endpoint public
• Adds a persistence unit "rolldown" to roll down the DB. For production it is be the beta database, for beta it is the alpha database
• Adds the code to roll down the MaTI db for curation, easily extensible for the ABC literature system.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9412085	Triggered	Generic Password	1b46566	src/main/resources/application.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[abecerra]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

username and password in application.yml for local development were set before activating gitguardian. No security compromise

[mluypaert]

Will close and re-open this PR in attempt to retrigger PR validation actions (which are currently being skipped, probably because the PR message body was edited shortly after PR creation)..

[mluypaert]

Will close and re-open this PR in attempt to retrigger PR validation actions (which are currently being skipped, probably because the PR message body was edited shortly after PR creation)..

Close & reopen did the trick, PR validation is running now: https://github.com/alliance-genome/agr_mati/actions/runs/7846680755?pr=72