Upgrading to dotnet 7 because the blazor wasm got much improvemnts over 6.0

[paule96]

It would be nice if we could use the newer dotnet, at least for Blazor.

In special the new multithreading looks interessting.
https://devblogs.microsoft.com/dotnet/asp-net-core-updates-in-dotnet-7-rc-2/#webassembly-multithreading-experimental

I guess it can be nicely combined with the compression we plan in #20

[paule96]

I guess we will now just upgrade, without taking all the advantages. There are to many blockers right now. For example for multi threading we would need the following:

• a way to set headers while debugging (issue here)
• our deploy script must be able to deploy a static webapp config
• it's experimental so 🤷‍♀️

[paule96]

one other thing that holds back a bit a clean update, is the support for our build dependcies. Currently dart sass builder only supports dotnet 6. So we need to install both in our pipeline.
PR for that is here: deanwiseman/DartSassBuilder#24

Another way would be to remove this build dependency

[paule96]

So the learning of tonight is we are technical able to deploy azure functions with dotnet 7. The problem is, that this is currently not supported in the managed azure functions feature of azure static webapp.
But because this webapp should be stupid and simple, we won't upgrade now.

https://learn.microsoft.com/en-us/azure/static-web-apps/apis-functions#constraints

Opened an issue to clarify what's going on. Azure/static-web-apps#1016

[paule96]

we finished the work here. We are now fully migrated to .NET 7.0. It was merged with #32 and #29