Sync repo root level config files

[surchs]

Once #43 is closed, we will be pushing the auto release workflow to all/most repos. But in order to work in other repos, we also have to manually add a .autorc config file to each repo's root directory. There are other files like this that we want to push to many repos / keep the same across repos.

We could:

• Add a new template_config directory that contains config files all repos should have. AND/OR
• Add a python-specific config directory, for root level files that only python repos need (e.g. .precommit ?)
• same for the JS/Vue repos?

The https://github.com/neurobagel/workflows/blob/main/.github/sync.yml config file here let's us define for each template_directory where in the target repo the files should be copied. We may have to create a completely new sync-workflow with a completely new config file if we also want to change the list of repositories that files get pushed to (e.g. only the python repos...). Should investigate this

edit: it's actually very easy to make multiple groups (e.g. "all repos", "python repos", "js repos", "...") with the action we are using: https://github.com/BetaHuhn/repo-file-sync-action?tab=readme-ov-file#sync-the-same-files-to-multiple-repositories 🎉

related:

• Add codespell as a synced workflow #90
• Add flake8 to synced workflows #91
• Add nightly docker build to synced workflows #92
• Add pytest workflows to synced workflows #93

[github-actions]

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!

[github-actions]

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!