fix: Modified to not run the full metadata tests in some circumstances

[jcpitre]

Summary: closes #655

• Added code to exclude classes from integration test.
• Modified integration test action so we exclude the metadata tests if the trigger is catalog-sources-updated, i.e. it comes from the mobility_database_repo.
• We still want to keep the health check in all cases (it yells us if we can talk to the API at least). Separated metadata tests into basic and normal.
• The basic just make sure the API values returned have the right format.

Expected behavior:

Integration should not fail for no good reason.

Testing tips:

• Ran integration-test.sh locally with the -x or -c arguments
• e.g. ./scripts/integration-tests.sh -u http://0.0.0.0:8080 -f "$FILE_PATH" -x MetadataEndpointTests
• check in the output that MetadataEndpointTests is not run.

I also tested with the GH actions, but the possibilities are limited. Here are the temporary changes I did in a testing branch:

• Added the trigger push to branch to db-update-prod.yml
• Kept only update-qa and integration-tests-qa jobs in that file. Commented out the other jobs.
• Modified the health_check step in integration-test.yml so the we check for "push" instead of "repository_dispatch"

I pushed the testing branch and the db-update-prod.yml is run. Make sure MetadataEndpointTests is not run in Health Check and Run Integration Tests steps

Please make sure these boxes are checked before submitting your pull request - thanks!

• [x] Run the unit tests with ./scripts/api-tests.sh to make sure you didn't break anything
• [ ] Add or update any needed documentation to the repo
• [x] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
• [x] Linked all relevant issues
• [ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)