Java code generation issue with `azure-native:apimanagement:LLMDiagnosticSettings`

What happened?

There's a name collision in the schema for 3.0.0 (also present for 3.1.0): azure-native:apimanagement:LlmDiagnosticSettings and azure-native:apimanagement:LLMDiagnosticSettings. The keys are the same, just the case is different.

See schema:

Both types are generated in Java (see:
com.pulumi.azurenative.apimanagement.enums.LlmDiagnosticSettings and
com.pulumi.azurenative.apimanagement.inputs.LLMDiagnosticSettingsArgs). LlmDiagnosticSettings should be referenced in one of the fields in LLMDiagnosticSettings, however this is the code that is actually generated in Java:

I don't think LlmDiagnosticSettings is ever used.

I haven't tried running this, so I'm not sure if it leads to any exceptions being thrown or anything.

Example

All relevant details have been provided above.

Output of pulumi about

Irrelevant, this is about the generated code.

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Start by comparing the 3.0.0 and 3.1.0 schema entries for LlmDiagnosticSettings and LLMDiagnosticSettings, then inspect how they produce com.pulumi.azurenative.apimanagement.enums.LlmDiagnosticSettings and inputs.LLMDiagnosticSettingsArgs. Done means the generated Java uses the intended enum reference without a case-collision or unused generated type.