refactor: add clinical and data-submission to docker-compose WIP

[JamesTLopez]

WIP, will update relevant docs or readme's once confirmed this is the solution going forward.

Current Changes

• Add clinical-submission to docker-compose
• Add dictionary-manager to docker-compose
• Add db for clinical-submission to docker-compose
• Add db for dictionary-manager to docker-compose
• Update services naming to better reflect the type of service it represents
• Add .env.clinical.schema example file
• Change DACO-API port to 3001 (dictionary-manager is fixed to 3000)
• Change API_URL in UI to 3001

Special Instructions

You will need to copy and remove .schema from .env.clinical.schema and fill in the values. If you have clinical-submission repo already running, you can just copy that into daco/api/.env.clinical ( @demariadaniel Please reach out to me, and I will whisper the relevant authz vars to get started)

1. Remove all containers from docker `pcgl-daco-database` so we can update the names 
2. In file .env.clinical, Ensure that values are `DB_HOST=host.docker.internal`, `LECTERN_URL=http://host.docker.internal:3000` and `AUTH_ENABLED=true`
3. docker-compose up -d to relaunch the services.

Summary

Related Issues

• Paste URL to issue 1
• Paste URL to issue 2

Description of Changes

Readiness Checklist

• Self Review
  • I have performed a self review of code
  • I have run the application locally and manually tested the feature
• PR Format
  • The PR title is properly formatted to match the pattern: #{TicketNumber}: Description of Changes
  • Links are included to all relevant tickets
• Labels Added
  • Label is added for each package/app that is modified (api, ui, data-model, etc.)
  • Label is added for the type of work done in this PR (feature, fix, chore, documentation)
• Local Testing
  • Successfully built all packages locally
  • Successfully ran all test suites, all unit and integration tests pass
• Updated Tests
  • Unit and integration tests have been added that describe the bug that was fixed or the features that were added
• Documentation
  • All new environment variables added to .env.schema file and documented in the README
  • All changes to server HTTP endpoints have open-api documentation
  • All new functions exported from their module have TSDoc comment documentation