Auto publish to PyPI, Github release and docs on tag

[multimeric]

Closes #81, closes #64

[multimeric]

Hi @pr4deepr, can you please ensure that:

• There is a secret called TWINE_TOKEN associated with this repo which stores a PyPI token that has push permissions to both napari_lattice and lls_core. Should be configurable here
• The GITHUB_TOKEN has write permission. Should be configured here

This will give the workflow the permissions to push a release.

[pr4deepr]

• There is a secret called TWINE_TOKEN associated with this repo which stores a PyPI token that has push permissions to both napari_lattice and lls_core. Should be configurable here

There is a Twine token for the repo which I've used for automatic deployment to pypi before.

• The GITHUB_TOKEN has write permission. Should be configured here

Workflow permissions have: Read and Write permissions enabled.

[multimeric]

Okay great. The only issue is that it might not have permissions to push the lls_core package, because it doesn't exist yet. Anyway, once the other issues are fixed, I'll merge this and we can test out a release. It might not work the first time.

[multimeric]

Okay, this looks good. We'll have to merge this and then I'll push some tags directly to the repo in order to run the actual deployment. It probably won't work the first time but that's not a big deal.

[pr4deepr]

Thanks, just checking that updating docs will only trigger a docs specific workflow to update the site??

[multimeric]

Oh yeah true, there's no reason to limit the docs to only building when a new release is made

[multimeric]

Okay, I think this is failing to push the docs just because you haven't granted permissions for pull requests to do that, which is a good practice:

So this should work once this is merged.

[pr4deepr]

Actually, I was looking at this now
seems to be already checked as I have used workflows before in this repo