Add action to build releases

[cgarling]

Closes #8.

This adds a manually triggered action to follow the steps in create_database.sh (I wrote the steps into the action itself, it doesn't actually use create_database.sh) and stage the output files as a github release. When manually triggered, the action will ask for a tag identifer, release notes, and there is an additional toggle to disable creating a release (you can toggle this off to do a "dry run").

You will see I made some additional changes to facilitate running on CI.

• Mismatch between filename and key of ngc_0185_gc_pa-n185 was breaking build, fixed
• path specifiers in some of the python files were brittle with respect to whether LVDBDIR environment variable had an ending '/' or not, used pathlib to harden this
• Missing publishers for books in the lvdb.bib were causing issues so I added those (maybe this is not actually a fatal error, but I was troubleshooting failures and thought this would fix it; left it in anyway)
• Removed duplicate entries in lvdb.bib (I think this was actually what was causing the builds to fail, not the missing publishers, but oh well)

See successful build run here:
https://github.com/cgarling/local_volume_database/actions/runs/25891102793/job/76094209244

which created this release: https://github.com/cgarling/local_volume_database/releases/tag/test1

You can peruse the files it created and see if anything is missing or looks incorrect. Let me know what you think, happy to iterate on this

[apace7]

This is really cool to see. This is going to take me a bit to work through.