Use Target Type new only when apparent

[stefannikolei]

Prerequisites

• I have written a descriptive pull-request title
• I have verified that there are no overlapping pull-requests open
• I have verified that I am following the existing coding patterns and practice as demonstrated in the repository. These follow strict Stylecop rules 👮.
• I have provided test coverage for my change (where applicable)

Description

[Copilot]

Pull Request Overview

This PR enforces explicit type constructors instead of target-typed new(...) in places where the target type is not immediately obvious. It updates calls across image processing extensions, primitive types, pixel formats, metadata profiles, and memory management APIs to use new Type(...) or new Type[] syntax explicitly.

• Replaced ambiguous new(...) expressions with new Rectangle(...), new Size(...), new Vector2(...), new Vector4(...), etc.
• Updated collection and metadata initializers to use explicit type names.
• Refactored image and memory-related constructors to avoid relying on target-typed new.

Reviewed Changes

Copilot reviewed 300 out of 703 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
ResizeExtensions.cs	Changed new(…) to new Rectangle(…) in resize overloads.
Primitives/SizeF.cs, Size.cs	Replaced new(…) with new Vector2/SizeF(…) in transforms.
Primitives/RectangleF.cs, Rectangle.cs	Made rectangle constructors explicit.
PixelFormats/**	Updated pixel constructors (Vector4, Vector2, Rgba32).
Memory/UnmanagedMemoryManager{T}.cs	Made Span<T> and MemoryHandle constructions explicit.
Metadata/Profiles/ICC/DataReader/IccDataReader.TagData	Changed tag entry new(…) to new Icc…(…).
Image{TPixel}.cs, ImageFrame{TPixel}.cs	Expanded new() calls for ImageMetadata and ImageFrameMetadata.

[stefannikolei]

@JimBobSquarePants i also opened a PR in the SharedInfrastructure project.

[stefannikolei]

@JimBobSquarePants Updated the shared-infra submodule