chore(deps): update dotnet monorepo to v9 (major)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
mcr.microsoft.com/dotnet/aspnet	final	major	8.0-bookworm-slim -> 9.0-bookworm-slim
mcr.microsoft.com/dotnet/aspnet	final	major	8.0 -> 9.0
mcr.microsoft.com/dotnet/sdk	stage	major	8.0-bookworm-slim -> 9.0-bookworm-slim
mcr.microsoft.com/dotnet/sdk	stage	major	8.0 -> 9.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[waghanza]

cc @ShreyasJejurkar @i4004 @dj-nitehawk @beetlex-io

[waghanza]

@ShreyasJejurkar do you have an idea of a release data for dotnet 9, I mean final stage ? not any RC

[ShreyasJejurkar]

@waghanza it will be in November.

[waghanza]

@ShreyasJejurkar dit net 9 will not be an LTS ?

[ShreyasJejurkar]

.NET 9 won't be LTS. But that should not be a reason not to run benchmarks on 9.
All LTS and non LTS releases are bullet tested and has quality fixes and perf improvements.

[waghanza]

The question is more what we need to bench in priority.

I think LTS should be first, this is a valuable argument when choosing a new stack.

However, I have not said that STS should not be tested, but not the priority.

PS : I try to define the same policy for all languages, and for example you have LTS concept in nodejs, but not STS one