Plan for rust based nix-installer to be integrated into the nix release process / repo, plans forward

Is your feature request related to a problem?

Now that nix-installer has been brought up to date by @Mic92, we have the procedural issues to figure out. I see a lot of unanswered questions:

• How do we maintain that and include in releases? Do we integrate that fully into the nix release process and upload the artifacts directly into the nix-releases bucket? That seems like the best sounding approach to me.
• How is the installer versioned and maintained across release branches?
• Redirects from https://nixos.org/download. Current installer writes to the nix-channels bucket to change a symlink pointing to the latest release. Do we want something similar for the rust based installer? Do we maybe also want to start differentiating latest/latest stable release too?
• What do we call the installer? installer-ng maybe so that there's less confusion?
• Do we maybe merge the repo entirely? Doesn't seem like there's much benefit to having that be a separate repo? (modulo CI concerns voiced by @Mic92)
• How do we update the artifacts with security releases and such?

Proposed solution

None really, but I'd like to see a sustainable solution agreed upon, process established and documented. Ideally a team member would also be responsible for maintaining the installer (relying solely on @Mic92 isn't sustainable).

Alternative solutions

Additional context

Checklist

• checked latest Nix manual (source)
• checked open feature issues and pull requests for possible duplicates
• reviewed the contributing guide

---

Add :+1: to issues you find important.