Shorten tracebacks for errors

[alyssadai]

The tracebacks are currently quite long and difficult to parse. We should try and limit the error output to the informative message and what's necessary for the user to identify the issue in their input.

We may want to also consider https://typer.tiangolo.com/tutorial/terminating/#exit-with-an-error where it makes sense for upfront checks.

See also https://github.com/neurobagel/bagel-cli/pull/212#discussion_r1337604637

• [ ] maybe make this configurable via a flag

[surchs]

162 seems related, let's handle those together and not deal with the present issue now

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