chore(deps): update aspire to 13.1.3

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Aspire.AppHost.Sdk	msbuild-sdk	patch	13.1.2 → 13.1.3
Aspire.Hosting.AppHost	nuget	patch	13.1.2 → 13.1.3
Aspire.Hosting.PostgreSQL	nuget	patch	13.1.2 → 13.1.3
Aspire.Hosting.RabbitMQ	nuget	patch	13.1.2 → 13.1.3
Aspire.Hosting.Redis	nuget	patch	13.1.2 → 13.1.3
Aspire.Hosting.Testing	nuget	patch	13.1.2 → 13.1.3
Aspire.Npgsql.EntityFrameworkCore.PostgreSQL	nuget	patch	13.1.2 → 13.1.3
Aspire.StackExchange.Redis	nuget	patch	13.1.2 → 13.1.3
Aspire.StackExchange.Redis.OutputCaching	nuget	patch	13.1.2 → 13.1.3

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[claude]

This is a Renovate bot-generated patch dependency update, bumping all .NET Aspire packages uniformly from 13.1.2 to 13.1.3.

What the PR does: Updates 9 Aspire packages (Aspire.AppHost.Sdk, Aspire.Hosting.AppHost, Aspire.Hosting.PostgreSQL, Aspire.Hosting.RabbitMQ, Aspire.Hosting.Redis, Aspire.Hosting.Testing, Aspire.Npgsql.EntityFrameworkCore.PostgreSQL, Aspire.StackExchange.Redis, Aspire.StackExchange.Redis.OutputCaching) consistently across:

• Directory.Packages.props (centralized package management)
• TUnit.Templates/content/TUnit.Aspire.Starter/ (starter templates)
• examples/CloudShop/ (example projects)

Assessment:

• Version bump is consistent: every occurrence of 13.1.2 for these packages is updated to 13.1.3 - no version skew introduced.
• This is purely a dependency version change with zero logic modifications, so there are no AOT compatibility, dual-mode (source-gen/reflection), or performance concerns.
• The Aspire packages are only used in example and template projects, not in the core TUnit engine, so there is no risk to the testing framework itself.
• The Directory.Packages.props central version management entry is updated alongside the individual project references that pin their own versions (template/example projects don't use CPM), which is correct.
• Auto-merge is already enabled, which is appropriate for a routine Renovate patch update like this.

No issues found. This is a safe, routine dependency maintenance update.