[ENH] Provide instructions for federation API

[surchs]

• Closes document how to run F-API locally #129

Changes proposed in this pull request:

• remove query tool deployment from the default docker stack (needs changes to the docker-compose.yml file, e.g. here Store all Compose files and configs in one place recipes#1)
• provide new "optional" section on query tool deployment
• new page on "local federation"

Checklist

• PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF]) (see https://neurobagel.org/contributing/pull_requests for more info)
• PR links to GitHub issue with mention Closes #XXXX
• Checks pass

[netlify]

✅ Deploy Preview for neurobagel-documentation ready!

Name	Link
🔨 Latest commit	d073c87
🔍 Latest deploy log	https://app.netlify.com/sites/neurobagel-documentation/deploys/6565fab3a75203000800365c
😎 Deploy Preview	https://deploy-preview-133--neurobagel-documentation.netlify.app/federate
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[alyssadai]

Thanks for all this great documentation @surchs!

The overall order and grouping of the new instructions make a lot of sense to me, and I do feel this separation of the query tool from the main API-graph stack makes things a little easier to understand.

I've added suggestions below which are mostly related to clarity and minor config fixes (it looks like GitHub is hiding a bunch of them under the "hidden conversations"), along with a few questions that may warrant some new issues to address.

Have a look and see what makes sense to you.

A general comment: it looks like our inline capitalization of "Neurobagel" varies a lot across our docs. Maybe worth converging on one standard capitalization (either "neurobagel" or "Neurobagel")?

[alyssadai]

One 🍒, otherwise good to go! 🎉 Thanks again for all your work on this @surchs!