feat(rust): Adds Rust CI/CD and Refactors Cataylst gateway to be passing (minus unit tests).

[stevenj]

Description

Thanks for contributing to the project!
Please fill out this template to help us review your changes.

This is currently linked to a pre-release of the rust tooling defined in catalyst-ci.
That will be changed in a separate PR once the upstream code merges.

Related Issue(s)

List the issue numbers related to this pull request.

• Closes: feat: Feature/poem migration start | NPG-0000 catalyst-core#538
• Closes: 🛠️ [TASK] : Ensure Markdown and Spelling lints pass after cat-data-service migration #41
• Closes: 🛠️ [TASK] : Ensure cat-gateway passes Clippy pedantic lints and Documentation checks. #43
• Closes: 🛠️ [TASK] : Ensure cat-gateway is properly building its deployable container in CI #44
• Closes: 🛠️ [TASK] : Rename cat-data-service to Catalyst Data Gateway or cat-gateway for short. #39

Description of Changes

• Add Earthly defined Rust CI Runners following convention agreed with @jmgilman
• Refactors Cat-Data-Service into the first iteration of Catalyst Gateway
• Makes all lints pass at the new strict levels. Code builds.

Breaking Changes

Tests currently do not pass since they are blocked on refactoring the DB setup.

See:

• 🛠️ [TASK] : Fix testcases that fail clippy lint checks #68
• 🛠️ [TASK] : cat-gateway must be resiliant in the face of DB schema changes #46
• 🛠️ [TASK] : cat-gateway health endpoint to probe schema version #47
• 🛠️ [TASK] : cat-gateway DB Migratiosn to be able to run in a incremental, or Drop and reload fashion. #48
• 🛠️ [TASK] : cat-gateway needs to be locally deployable for testing. #49

This should still be merged even with the tests broken, and they can be corrected in a followup.

Please confirm the following checks

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream module

[minikin]

@stevenj
I've approved this PR.
Moving forward, I propose we aim for more concise PRs.
Smaller PRs can streamline the review process and save time for everyone involved