Branch workflows and tidy up

[marcus-j-davies]

@crxporter @Shaquu

I'm going to :

• Update the release page to include 0.9.0

• Update the npm publish workflow to trigger on GitHub release (instead of push)

  This will also apply to pre-release versions (that I will use on the dev branch)
  This allows me to push to these branches, without an unwanted release happening

• Remove the publish-gpr step (Have never seen it work)

• Recreate the dev branch (its all over the place) - to mirror main as it currently is.

Then my workflow will be.

New branch based on dev (for what ever change im doing - but a branch will now be optional, small changes I wont) ->
PR to dev -> GH pre-release (NPM publish - dev)
PR to main (from dev) -> GH release (NPM publish - prod)

The reason I'm going to switch to a release trigger, is to allow us the ability to commit changes to the dev branch, without a release on NPM each time (same goes to main) only when a release is ready, will it hit NPM

These steps, should allow a clean working environment, and match GitHub release entries with NPM
(creating a release in GH, will publish to NPM)

any objections?