Add sample Temporal integration for Aspire

[cecilphillip]

What was changed

This PR adds comprehensive .NET Aspire integration for Temporal, including:

• Custom Aspire resource definitions for Temporal server deployment with three deployment models:

  • Local test server using Temporalio.Testing.WorkflowEnvironment
  • Container-based deployment using Docker
  • CLI-based server for environments without Docker

• Temporal.Extensions.Aspire.Hosting library with:

  • Extension methods for adding Temporal resources to Aspire applications
  • Health check integration for Temporal connectivity
  • Automatic service discovery and environment variable injection
  • Resource lifecycle management (start/stop) via Aspire dashboard
  • Configurable options for ports, namespaces, search attributes, and dynamic config

• Sample Aspire application demonstrating the integration:

  • TemporalioSamples.SampleAppHost - Aspire app host configuring Temporal resources
  • TemporalioSamples.SampleWorker - Worker service consuming workflows/activities
  • TemporalioSamples.SampleClient - Client triggering workflow execution
  • TemporalioSamples.SampleWorkflow - Simple workflow and activity definitions

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cretz]

Aren't you supposed to be able to use Aspire to get client connectivity information too? Even if it is powered by env vars under the hood, one might expect a type-safe Aspire way to get a client or client options for the given "temporal" reference from other project.

[cecilphillip]

Aspire only does that through environment variables. There isn't anything type-safe configuration support specifically from aspire. Typically library authors would create their own using Microsoft.Extensions.Configuration bindings

[cretz]

I mean from a caller POV. For instance, stuff like https://aspire.dev/integrations/databases/postgres/postgres-get-started/?lang=csharp#use-the-integration-in-client-projects. I would expect that you can just put a client on the DI container w/ a single Aspire helper. Sure you can always still manually create clients.

[cecilphillip]

I mean we could create an extension method that makes that a little nicer, but that would be a client specific library/package. From an aspire API perspective, they just inject configuration properties that get consumed .

[cretz]

They inject configuration properties for those not wanting to use the helper, but they also provide a helper. I figure the nice aspect of "Aspire helper to make server, Aspire helper to make client" is valuable even though they can use the env vars directly of course, same as Postgres there.