Reorg layout

[Rosuavio]

Step towards #3594

Reorganize some of the layout controls.

Moved the code in Controls.Layout into Controls.Primitives.
Moved LayoutTransformControl, HeaderedContentControl, HeaderedItemsControl, ListDetailsView, Carousel, OrbitView, BladeView, Expander, GridSplitter into Controls.Layout

PR Type

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Pull Request has been submitted to the documentation repository instructions. Link:
• Sample in sample app has been added / updated (for bug fixes / features)
  • Icon has been created (if new sample) following the Thumbnail Style Guide and templates
• New major technical changes in the toolkit have or will be added to the Wiki e.g. build changes, source generators, testing infrastructure, sample creation changes, etc...
• Tests for the changes have been added (for bug fixes / features) (if applicable)
• Header has been added to all new source files (run build/UpdateHeaders.bat)
• Contains NO breaking changes

Other information

[ghost]

Thanks RosarioPulella for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌

[michael-hawker]

@RosarioPulella couple of test failures, assume string resource lookup related:

Taking a quick look...

[michael-hawker]

Ah, you forgot to split the Generic.xaml file into the Layout package, checking if that's fixing the tests locally.

[michael-hawker]

@RosarioPulella looks like removing the primitives was only a 5kb difference in our practical test, so pretty minimal without any of the XAML components. For now though still good to try and keep things isolated, but good to know for the future if we build more complex controls that if we have XAML-less ones they're easy to reference without much ramification.

I think the main thing we're just starting to learn some of these general patterns about what makes things bad or worse. Once we get shipping, we can investigate how we can store our baseline numbers and have PRs compare against that for us to detect any large swings before they get integrated. I was thinking we could just have a dedicated repo for that which could be easy to have the CI commit updates to when something is merged to main.

It's interesting that overall we only saw about a 400kb decrease to the core package by pulling out the Layout controls. I'm curious how the Input package next will fair.

[michael-hawker]

@RosarioPulella this seems like a good change, I think this would be ready to merge into the dev branch, eh? Any concerns or other things we should check?

[Rosuavio]

It should be ready now, doing some last checks but I'll take it out of draft. Ready @michael-hawker

[Rosuavio]

Almost forgot to split out the DesignTools project for the layout controls.

[michael-hawker]

Forgot to update the strings, see f3547fe, not sure if you want to cherry-pick or just have that forward-fixed?

[Rosuavio]

Just cheery picked, should be ready now.

[michael-hawker]

Thanks @RosarioPulella, I'll merge this once the CI passes and then we can close out the Input PR next. 🎉