Automate GraphDB setup

[surchs]

A user who has just spun up our tool stack (e.g. API + Graph, neurobagel/api#90) still has to:

1. create a user or change the admin user password
2. create a new graph database

and then

• put data in the new graph database
  • already made automatic by add_data_to_graph.sh

all but this last step could and should probably be done automatically.

We should:

• write a script that uses variables set in the .env file to populate the curl commands needed for the user and database set-up, and then runs them all automatically

This helps us address two use cases:

1. A user is creating a new deployment and wants to be immediately ready to get started with a database and user
2. It allows us to quickly spin up a working environment for development (with some example data)

[surchs]

The description in https://www.neurobagel.org/documentation/start/#setup-for-the-first-run should be a good template for automating this most of the way.

[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 stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

[surchs]

This issue needs more focus, we should update the description to

• flesh out what an automatic graph deployment actually means
• if we have already done this

@surchs and @alyssadai , please clarify

[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!

[surchs]

👀 -> 🎉 ?