Add check adminRepoCreationOnly

[UlisesGascon]

Main Changes

• Enable check adminRepoCreationOnly in the compliance_checks table (b14821b)
• Add check validator for adminRepoCreationOnly (fdd8199)
• Add check adminRepoCreationOnly (0c8b874)

Other Changes

• Revert boolean logic to match validation criteria (fb7996c)

Context

Close #75

Changelog

• b14821b feat: enable check adminRepoCreationOnly in the compliance_checks table by @UlisesGascon
• fdd8199 feat: add check validator for adminRepoCreationOnly by @UlisesGascon
• 0c8b874 feat: add check adminRepoCreationOnly by @UlisesGascon
• fb7996c fix: revert boolean logic to match validation criteria by @UlisesGascon

[github-actions]

It looks like you've made changes to the migrations. Thanks for your contribution!

• Have you run npm run db:generate-schema to ensure the updated schemas are included in your PR?
• Have you run npm run db:migrate and then npm run db:rollback to confirm that rollbacks are working as expected?

Note: Please avoid making changes to existing migration files, as they won't be executed again in deployed environments.

[github-actions]

It looks like you've made changes to the compliance checks. Thanks for your contribution!
Here are some questions to ensure your changes are complete. Please feel free to ignore the ones that are not relevant:

• Have you run npm run db:generate-schema to ensure the updated schemas are included in your PR?
• Have you run npm run db:migrate and then npm run db:rollback to confirm that rollbacks are working as expected?
• Have you updated the compliance check in the compliance_checks table?
• Have you included a specific validator (src/checks/validators/) for this check with unit tests (__tests__/checks/)?
• Have you included a specific file in src/checks/complianceChecks with the integration tests (__tests__/checks/)?
• Have you included severity validation (getSeverityFromPriorityGroup)?
• Have you included the tasks, alerts, and results in the database tables?
• Have you tested the check with check run --name {check_code_name} using the seeded database (npm run db:seed)?
• Have you created a PR in the website with the calculation details?

You can find more information in the contributing guide.