feat(dotnet): support multiple configurable REST resources

[colbytimm]

Summary

Ports the multi-resource capability (already merged for the Python and TypeScript templates) to the .NET template. A resources list in copier.yml now drives the generated layers so a single generated project can expose N resources, each with:

• its own URL endpoint,
• a storage container (resources sharing a container id share storage),
• a chosen subset of operations (list, get_by_id, create, update=PATCH, replace=PUT [new], delete).

The default value is a single resource matching the project name with today's CRUD behaviour, so answering only project_name reproduces the original single-resource project (no PUT). PUT/replace is opt-in.

Approach — per-resource named types

Each resource generates its own named types — Cat, CatController, CatService, CatRepository, CatDto, CreateCatRequest, ICatController, … — rather than a shared generic Item* set. Because Copier cannot fan a resource out into separate files, all per-resource classes for a layer live in one file behind a {% for resource in resources %} loop.

• Controllers & services expose exactly one method per operation the resource declares (per-op {% if "op" in resource.operations %} gating on both the interface and the implementation). Repositories stay a full data-access layer (all six operations) regardless of the subset.
• ReplaceAsync (full-document overwrite) is implemented across Cosmos DB, Firestore, and DynamoDB.

Changes

• dotnet/copier.yml — add a validated resources question (PascalCase name, kebab-case endpoint, valid container id, ≥1 valid operation, unique names/endpoints).
• Layers — Models (entities/DTOs/requests/validators), Interfaces, Controllers, Services, Repositories loop over resources and emit a named class/interface per resource; controller/service methods and their request types are gated per operation.
• Wiring — DependencyInjection registers a per-resource I<Resource>Controller, each bound to its storage container (Cosmos container / Firestore collection / DynamoDB table) resolved by name from settings; resources sharing a container id resolve the same handle.
• Per-cloud routing (in-file Jinja loops):
  • Azure — ItemFunctions injects per-resource controllers and exposes looped [Function] methods (Get, GetList, Create, Update, Replace, Delete) + Health.
  • GCP — Function.cs injects per-resource controllers and dispatches by endpoint → method → id-presence, with per-operation 405 gating.
  • AWS — ItemFunctions injects per-resource controllers; template.yaml emits one AWS::Serverless::Function per resource×operation, one DynamoDB table per distinct container, plus a Health function.
• Per-container settings — Azure CosmosDbContainerName_<Container>, GCP FIRESTORE_COLLECTION_<Container>, AWS DYNAMODB_TABLE_NAME_<CONTAINER>.
• Tests — unit tests loop per resource with per-operation gating (controllers/services); repository tests stay full.
• README — endpoint list loops over the configured resources/operations.

Verification

Rendered all 3 clouds × 3 fixtures (single default; two resources / separate containers / mixed ops incl. PUT; two resources sharing one container with different op subsets) with copier copy --trust:

• All 9 renders succeed; all generated .cs files are brace/paren-balanced; no residual generic Item* domain types leak into output (the host wiring class keeps the internal ItemFunctions name, referenced by the AWS handler strings).
• Operation subsetting is exact per fixture (controller/service expose only the chosen operations; GCP returns 405 for disabled methods; SAM emits only the chosen functions).
• Shared container ⇒ both resources resolve the same container/collection/table env var; separate ⇒ distinct ones.
• Default fixture renders types named after the project with the legacy 5 operations (no PUT), staying behaviourally equivalent to the pre-feature output.
• The validator rejects invalid input (e.g. a non-PascalCase resource name).

No local .NET SDK is available in this environment, so the build/test is validated via the build-dotnet CI pipeline on this PR.

🤖 Generated with Claude Code

---

Generated by Claude Code