Enable AOT (Ahead-of-Time) Compilation in Tests

## Background

While the original "why" behind AoT being disabled in tests is lost or unknown, the "why" behind enabling it now is known.

We are in the process of collecting and fixing the NativeAoT issues in the toolkit.

## Problem

We'd like to be able to test more of the codebase with AoT than the sample app provides.

We could use our test projects, but AoT would need to be enabled.

## Solution

Due to the nature of tests using shared projects, we're not able to toggle AoT for them individually.

We'll have to either *enable csproj support for tests* (see https://github.com/CommunityToolkit/Tooling-Windows-Submodule/issues/101) or *enable aot in all test projects simultaneously.*

We've made progress towards AoT recently, but the Gallery App can only tell us so much. We'll need the ability to validate AoT issues using unit tests to ensure proper coverage long-term.

Start by reviewing how the shared test projects are configured and the linked issue about enabling csproj support for tests. Compare enabling AoT across all test projects with adding csproj support, and consider the Gallery App and unit-test coverage as validation points. Done means the test projects can exercise and validate NativeAoT issues long-term.

Scritto dal modello di indicizzazione a partire dal testo della issue.