Upgrade to .NET 8

[danielchalmers]

Project structure is now closer to the default .NET 8 Blazor templates.
Upgraded all packages (fixes some vulnerabilities).
Should be strictly WebAssembly with specifically no prerendering.

Some resources I used:

• https://github.com/danroth27/Net8BlazorWebAssembly
• https://stackoverflow.com/questions/77503849
• .NET 8 Blazor Error 404 after upgrading from .NET 6 dotnet/aspnetcore#52710
• Out of the box .net 8 blazor project fails when navigating directly to a route that load a page with injected dependencies. dotnet/aspnetcore#52614 (comment)
• https://learn.microsoft.com/en-us/aspnet/core/blazor/components/render-modes?view=aspnetcore-8.0#set-the-render-mode-for-the-entire-app
• Unable to route to Blazor component pages in the client assembly dotnet/aspnetcore#49313 (comment)

[danielchalmers]

Current issues:

• Have to scroll down to see page
• __Main is either not generated or simply not showing up
• Antiforgery preventing the ability to save snippets

Otherwise this brings the project up to date with modern Blazor practices.
Deadline is May when .NET 7 is EOL.

@Garderoben @mikes-gh When you find the time, could you look into the issues above to help me get this over the finish line? I will take another look as well after someone else has had a go. My branch is open to commits.

[mikes-gh]

@danielchalmers Sorry this diff is hard to review. I can't see anything about that relates to the issue which is the default assembly format change to wasm in net8. Perhaps you could try and reduce the diff. as a first step

[danielchalmers]

@danielchalmers Sorry this diff is hard to review. I can't see anything about that relates to the issue which is the default assembly format change to wasm in net8. Perhaps you could try and reduce the diff. as a first step

@mikes-gh I can't really reduce it because it's so intertwined due to rebasing the project on .NET 8 default template. A lot was changed by Microsoft and it would take twice as long to split it up