Several packages are incorrectly named on Nuget

[michael-hawker]

The Sizers are in the CommunityToolkit.WinUI.Controls namespace, but the package doesn't really reflect that.

The package name should have the Controls part in it as well, but currently it is omitted.

Not sure where that's getting dropped as it's in the project filename: CommunityToolkit.WinUI.Controls.Sizers.csproj.

But the package is instead CommunityToolkit.WinUI.Sizers.

[Arlodotexe]

@michael-hawker We'll get that fixed. That means we'll need to mark the published CommunityToolkit.WinUI.Sizers package as deprecated as well, how do we go about that?

[Arlodotexe]

Possibly the same issue with the Primitives package? It should be CommunityToolkit.WinUI.Controls.Primitives if it's based on the file name 🤔

[Arlodotexe]

Same problem with Triggers. Something has clearly been misconfigured, and other packages may be affected. Needs investigation.

[michael-hawker]

Triggers I'm not sure if it needs it as they're not controls? Definitely Primitives.

To deprecate the package can be done in the Azure Artifacts. Not sure who has permissions to do that besides me, Sergio might.

[Arlodotexe]

@niels9001 The PackageId defaults to the name of the component. We should be setting the PackageId for these manually.

[Arlodotexe]

The packages renamed in these PRs need to be deprecated:

• Fixed PackageId for control-based components #63
• Renamed BehaviorsAnimations to Behaviors.Animations #64
• Fix package id for CameraPreview #104

[michael-hawker]

Unlisted the packages with the old identities.