[ENH] Added a subsection for participant-level results tsv in aggregate mode

[rmanaem]

Closes #97

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	5fa291b
🔍 Latest deploy log	https://app.netlify.com/sites/neurobagel-documentation/deploys/6532bb10c32300000878359d
😎 Deploy Preview	https://deploy-preview-105--neurobagel-documentation.netlify.app
📱 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]

Two 🍒, otherwise 🧑‍🍳 !

I can message the nipoppy folks regarding the broken link. Could you open an issue to update the markdown-link-check config to ignore the broken SNOMED URL?

EDIT: Michelle has fixed the nipoppy link, and somehow the SNOMED URL redirection issue has fixed itself. I think all that's left to do is update this branch with the changes to main!

[alyssadai]

@rmanaem, I had another thought. What do you think about also updating the graph setup page in this PR to explicitly point to the query tool documentation page (https://neurobagel.org/query_tool/) for more info on running cohort queries?

i.e., maybe in this section

documentation/docs/infrastructure.md

Line 146 in 12bccc3

However, in many cases you may want to make the API accessible by a frontend tool such as our [browser query tool](https://github.com/neurobagel/query-tool).

and/or this

documentation/docs/infrastructure.md

Line 189 in 12bccc3

By default, this will also deploy a local version of the [Neurobagel graphical query tool](https://github.com/neurobagel/query-tool).

Could be as simple as adding a line For detailed instructions on using the query tool, see [Running cohort queries](link).

The goal would be letting sysadmins know very clearly where to look for more info about the query tool results, etc. in case they are testing out the query tool immediately after deployment.