Automate version publishing

This would solve...

Related: #2277

Currently, four maintainers have the ability to publish undici. This has been working well for awhile, but there are a number of steps that we must do (that we don't even document). They include:

• Tagging version commit
• Pushing version bump to main including tags
• Creating a GitHub release

The implementation should look like...

We should utilize some level of automation to completely publish new version of undici (and subsequently undici-types).

I'm open to solutions but I think GitHub Actions is our best bet.

I have also considered...

I've used changesets a lot with work. It's mainly for monorepos, but I imagine it could be used for this too.

Additional context

At work we actually go a step further. No developers are allowed to publish to npm directly. Publish is only allowed by Bot users, and it must be configured through an automatic process in GitHub Actions. I think limiting us in that way is a step too far, but using a bot user for the publishing would be good.

Start with related issue #2277 and review how the repository currently tags the version commit, pushes the version bump to main, and creates a GitHub release. The work is done when publishing undici and undici-types is automated, including the listed release steps; no files or tests are named in the issue.