[Go]: Avoid name collisions of case-sensitive properties

[thiagoarrais]

This PR changes the Go generator to avoid possible name collisions due to case-sensitive object property names. The input spec may specify two properties named Foo and foo, and the generated Go code would (before this PR) include two fields named Foo in the same struct.

This may be applicable to other languages as well.

Golang committee: @antihax @grokify @kemokemo @jirikuncar @ph4r5h4d @lwj5

PR checklist

• Read the contribution guidelines.
• Run the following to build the project and update samples (there were no modifications to sample outputs)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

---

Summary by cubic

Fixes Go code generation to prevent struct field collisions when properties differ only by case. Conflicting fields now get a stable P_ prefix so the generated code compiles and remains unambiguous.

• Bug Fixes

  • Detect collisions on Go field names and rename duplicates to P_<baseName>.
  • Mark renamed fields as sanitized to reflect the change.
  • Added a unit test covering name, Name, FirstName, first_name -> Name, P_Name, FirstName, P_first_name.

• Migration

  • If your schema defines case-sensitive duplicates, the generated Go field names may change to P_<baseName>. Update any references accordingly.

^{Written for commit b126649. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[Mattias-Sehlstedt]

I believe the best approach is to use the already existing name-mapping setting to handle these scenarios.

[thiagoarrais]

Closing in favor of name-mapping (pointed by @Mattias-Sehlstedt)