build: Update to net8.0 to fix canary

[Youssef1313]

GitHub Issue (If applicable): closes #

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting)
• Refactoring (no functional changes, no api changes)
• Build or CI related changes
• Documentation content changes
• Project automation
• Other... Please describe:

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested on iOS.
• Tested on Wasm.
• Tested on Android.
• Tested on UWP.
• Tested in both Light and Dark themes.
• Associated with an issue (GitHub or internal)

Other information

Internal Issue (If applicable):

[jeromelaban]

@Youssef1313 the migration is already done in the single project branch

[Youssef1313]

@jeromelaban The other PR isn't yet complete, doesn't adjust the CI for example. This was meant to be a quicker change to get canary working again soon, and possibly will make the single project migrarion easier as the CI will be set up right with .NET 8

[agneszitte]

@Youssef1313 I think the goal would be to do this work on the #1104 related changes. As the goal would be to migrate Gallery to single project as well. (Related discussion).

[Youssef1313]

@Youssef1313 I think the goal would be to do this work on the #1104 related changes. As the goal would be to migrate Gallery to single project as well. (Related discussion).

I guess we can make it in two steps, first updating to net8.0, which is more important for now, then continue the single project migration (which will mostly build on top of the net8.0 update).

[Youssef1313]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).