add an example script for registration

[alessandrofelder]

Description

What is this PR

• [ ] Bug fix
• [ ] Addition of a new feature
• [ ] Other

Why is this PR needed?

What does this PR do?

References

Please reference any existing issues/PRs that relate to this PR.

How has this PR been tested?

Please explain how any new code has been tested, and how you have ensured that no existing functionality has changed.

Is this a breaking change?

If this PR breaks any existing functionality, please explain how and why.

Does this PR require an update to the documentation?

If any features have changed, or have been added. Please explain how the documentation has been updated (and link to the associated PR). See here for details.

Checklist:

• [x] The code has been tested locally
• [ ] Tests have been added to cover all new functionality (unit & integration)
• [ ] The documentation has been updated to reflect any changes
• [x] The code has been formatted with pre-commit

[adamltyson]

@alessandrofelder before we need to start planning the 1st birthday party for this PR, do we still need it? I'm not clear on what it's for.

[alessandrofelder]

Thanks for the reminder @adamltyson . The idea is that it will become an example script (that we can benchmark) for brainreg - similar to the cellfinder one that @sfmig is working on currently. So hopefully can be merged in the next few weeks with the focus on benchmarking :)

[sfmig]

This PR was a first attempt to define a workflow for brainreg to later benchmark it.

We ended up focusing on the cellfinder case. Closing it for now, but we can reopen if/when we get back to this.