chore: update the release workflow

[agriyakhetarpal]

Description

Stemmed off from #618. This updates the release workflow prior to triggering a new v1.7.0 release.

Changes made

1. Better coloured output: FORCE_COLOR: environment variable set to 3
2. Workflow will now not be triggered from a tag but from a GitHub Release made from said tag (gives better control in case a tag is created and pushed to GitHub in haste)
3. Uses pypa/build to build the sdist and then the wheel from the sdist
4. Some bumps to GitHub Actions versions
5. The build and upload steps are now isolated, sharing artifacts. They are integrated with varying permissions to enhance security in the advent of events from malicious actors. The PyPI upload step uses the environment set in the repository settings and trusted publishing has been set up by @j-towns on the PyPI portal. The PyPI upload action runs twine internally with the strict option to check the sdist and wheel. It is pinned to the commit hash for the latest release at the time of writing (v1.9.0).

[agriyakhetarpal]

I shall take a look at the failing PyPy tests in a short moment

[agriyakhetarpal]

I faced the Pythran error in other repositories today and reported it a while earlier: pypa/setuptools#4579. It has been fixed with setuptools version 73.0.1, so I re-triggered the PyPy jobs. Please let me know if anything else is needed for the release after we merge this!