Document how to change docker compose `project` name

[alyssadai]

When spinning up multiple docker compose stacks (i.e., for different nodes), it is very helpful to use unique and informative compose project names so that:

• the running containers are easily identifiable by their prefixes.
• we can easily identify which volume to delete when resetting the graph instance for a given deployment / avoid name clashes
• users can continue to clone our neurobagel/recipes repo as is, without changing the destination directory name (which docker compose uses as its project name by default)

We already mention Docker's built in variable for this COMPOSE_PROJECT_NAME in our template.env file: https://github.com/neurobagel/recipes/blob/main/template.env#L17-L18

So all that's left is to mention this info in the docs (maybe the "Getting started" page?) and recommend that users change the name to something more informative.

[github-actions[bot]]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 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!