Create automation around releases

[MatthewCaseres]

As new features have just shipped and I would like to use them, I need the new code to be published. Often this is done with a GitHub action that publishes to PYPI on a new release.

• https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
• https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries

[lewisfogden]

I've got two things we need to sort before release, but almost there:

• need to add in a few Warnings for some of the functionality we are deliberately breaking (e.g. Tables no longer has a call(keys), getting rid of do_run=True)
• I've found an issue with the indexing in Tables - if you have multiple keys, an integer key going from 18-90 (say), and you look up 2, then you can get a false positive - it will find an earlier index. (2 would find the value for 90-16 for the prior key)

[lewisfogden]

Also - what are your thoughts on using poetry or another local build system? (I'm currently using hatch)

[lewisfogden]

I've published 1.0.5 using hatch, worked well.