Store all Compose files and configs in one place

[alyssadai]

We have a couple of deployment "flavours" now:

• n-API+graph docker-compose.yml + .env file
• f-API+query tool docker-compose.yml + .env file + .json (for node definition)
• n-API+graph+query tool

And we provide the template environment and docker compose files in a number of places, but mainly in the API repo. Instead we want to have a single place where we store all of the config and docker recipe files so we can

• Point a new user to this repo so that they can just clone all of the config files and none of the code
• Have a place where we can go to (automatically) test that all of our tools work well together
• Reduce the complexity of the config files and our docs about them, by splitting config into appropriate file names and file formats

We should store configuration-related files in a dedicated repo, maybe called recipes.
This repo should include configurations for each "flavour", ideally in separate subdirectories.

Existing files that would probably be affected as part of this issue:

• https://github.com/neurobagel/api/blob/main/.template-env
• https://github.com/neurobagel/api/blob/main/docker-compose.yml
• https://github.com/neurobagel/federation-api/blob/main/fed.env

We could also move our environment variable table into this repo, under a docs/ subdirectory.
https://github.com/neurobagel/api/blob/main/docs/api_environment_variables.tsv

Originally posted by @surchs in neurobagel/api#154 (comment)

Potentially of interest:

• multiple Compose profiles for a single docker-compose.yml: https://stackoverflow.com/a/65957695

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[alyssadai]

See also neurobagel/documentation#133

[neurobagel-bot]

🚀 Issue was released in v0.0.1 🚀