Use something like nightly.link or a non-re-published release to avoid excess notifications

[jcbhmr]

I've had this gripe for a while: I keep getting "dev: chore: publish binaries (#161)" notifications when i really only wanted to subscribe to the actual releases/prereleases.

I think now I finally have two options that id like you (cargo component peoples) to consider:

1. use plain old github actions artifacts to actions/upload-artifact@v4 for N days (yuou can change the days it retains) the nightly/dev builds and link to those using https://nightly.link or a bytecodealliance-controlled redirect-to-latest-artifact service that does the same thing as https://nightly.link
2. delete the assets and re-upload assets to the dev tag and just lock the dev tag at like the first commit or something so that it doesnt get re-published and trigger the notifications

i recently came across https://nightly.link and thought "oh hey that would be one way to solve this over-notification annoyance that i get from bytecodealliance/cargo-component". then after i thought about a while i thought that you could maybe get away with the current setup and just not re-publish the release but instead edit it in place so that notifs dont trigger.