[Testing] Add Analysis for Assembly Sizes

[michael-hawker]

Describe the problem this feature would solve

We should have a bot or something output the sizes of the assemblies so we can track changes to our package sizes and dependencies.

Describe the solution

I think the key is to figure out how much any particular package adds to the size of an application. However, dependencies that those packages pull in play a factor as well.

@azchohfi is thinking we'd have a csproj with build flags that would include the different assemblies and a mainpage.toolkit.uwp.ui.controls.xaml to pull in actual usage. Then we'd just build multiple times as part of our CI and could investigate output folder size of the AppX.

[ghost]

Hello, 'michael-hawker! Thanks for submitting a new feature request. I've automatically added a vote 👍 reaction to help get things started. Other community members can vote to help us prioritize this feature in the future!

[michael-hawker]

@azchohfi the build artifacts are where we can see the size of the end packages, eh? We should add some info to the wiki about how this works and how we can analyze this.

[azchohfi]

Yes, example:
https://dev.azure.com/dotnet/WindowsCommunityToolkit/_build/results?buildId=41520&view=artifacts&type=publishedArtifacts