Getting syncdbAfterWrite working

[zachmprince]

What is the change?

This PR modifies Database3.syncToSharedFolder so that it closes the h5py.File before trying to copy the h5 file to the working directory. The full process is:

1. Call h5py.File.close() and set the object to None.
2. Copy the h5py file to the working directory.
3. Garbage collect to avoid multiple database instances in memory.
4. Reload the h5 file in append mode

Tests were also added to ensure the syncDbAfterWrite setting behaves as expected.

Why is the change being made?

Partial resolution to #1794

Previously, setting syncDbAfterWrite caused a PermissionError due to the h5 file not being closed before trying to copy it.

---

Checklist

• This PR has only one purpose or idea.
• Tests have been added/updated to verify any new/changed code.

• The code style follows good practices.
• The commit message(s) follow good practices.

• The release notes have been updated if necessary.
• The documentation is still up-to-date in the doc folder.
• The dependencies are still up-to-date in pyproject.toml.

[john-science]

@zachmprince Remind me, did we run those downstream tests successfully? Last I heard, you sounded convinced, but were worried about some unrelated errors? How are you feeling now?

[zachmprince]

I am confident these changes are not affecting downstream applications. Test failure I ran into is unrelated. If you are okay merging it, please do! It's all okay on my side.