Determine `dotnetup` release branch strategy

### Prerequisites

- [x] I have read the [dotnetup documentation](https://github.com/dotnet/sdk/tree/release/dnup/documentation/general/dotnetup).
- [x] I have searched for [existing dotnetup issues](https://github.com/dotnet/sdk/issues?q=is%3Aissue%20state%3Aopen%20label%3Adotnetup).
- [x] I have searched for [existing dotnetup discussions](https://github.com/dotnet/sdk/discussions/categories/dotnetup).

### Issue type

Bug report

### Description

We were planning to use github releases but there was a pivot to use a daily build.
Currently CI uses the daily dotnetup build which is created from the internal pipeline using Arcade.
However, we need a way to:
1. Allow users to obtain historical releases
2. Maintain proper version bumps
3. Not break CI if dotnetup has a bug - isolate a 'preview' vs 'daily' type version or branch strategy
4. Consider tagging releases and when to have releases
5. Look at how other 'tip' based products we support (only latest is supported) work and ship today to consider how we'd react if we needed a rapid change to dotnetup due to a break and how others would 'roll-back' - since there is not yet automatic update, or how they automatically update and release.

First a plan should be outlined as a design doc.

Related
Automatic update https://github.com/dotnet/sdk/issues/50607
Automatic version updates https://github.com/dotnet/sdk/issues/50622

### dotnetup version

_No response_