Expand over sessions, update config call

[kaitj]

Proposed changes

Resolves #63 and took advantage to update the dependencies.

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you are unsure about any of the choices, don't hesitate to ask!

• Changes have been tested to ensure that fix is effective or that a feature works.
• Changes pass the unit tests
• Code has been run through the poe quality task
• I have included necessary documentation or comments (as necessary)
• Any dependent changes have been merged and published

Notes

All PRs will undergo the unit testing before being reviewed. You may be requested to explain or make additional changes before the PR is accepted.

[tkkuehn]

This looks good to me with a couple of caveats:

• Would be good to add a test case including a session (i.e. new test dataset under test, add a task to pyproject.toml, and add it to the test workflow)
• Not new to this PR, but we'll probably need to change inputs.subj_wildcards to a specific component .wildcards to handle the additional wildcards we don't care about in Add additional wildcard entities #69.

You can go ahead and merge once you add the test (assuming you agree it's worth adding)

[kaitj]

Fixed a couple of bugs with the sessions. @tkkuehn mind taking another look before I merge this in?

Will also look to move towards snakebids >= 0.8 in a separate PR. We can potentially think about creating a release from this and move the next version of snakebids and registration optimization, etc. in the next release.