gRPC SwaggerGen does not handle conflicting paths

[feiyun0112]

fix #64879

[dotnet-policy-service]

Thanks for your PR, @@feiyun0112. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[Copilot]

Pull request overview

This PR fixes an issue where gRPC SwaggerGen incorrectly generates conflicting OpenAPI paths for HTTP transcoding patterns that use the same variable name with different literal path segments (e.g., /v1/{name=widgets/*} and /v1/{name=things/*}).

Key Changes:

• Modified path resolution logic to include literal segments from multi-segment route patterns in the generated OpenAPI paths
• Added comprehensive test coverage for Google AIP-131 style resource patterns
• Ensures unique OpenAPI paths are generated even when gRPC patterns use the same parameter name

Reviewed changes

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

Show a summary per file

File	Description
GrpcJsonTranscodingDescriptionProvider.cs	Updated ResolvePath method to expand multi-segment variables by including literal segments, ensuring unique OpenAPI paths
resources.proto	Added test proto file defining a ResourceService with three methods using patterns with different literal segments
ResourceService.cs	Added test service implementation inheriting from generated gRPC service base
ResourcePathTests.cs	Added test validating that conflicting patterns generate unique OpenAPI paths with correct parameter mappings
Microsoft.AspNetCore.Grpc.Swagger.Tests.csproj	Added reference to the new resources.proto file for code generation