Support Forcing Unique Operation IDs (Fixes #910)

[wolveix]

This would close out #910.

Per that issue:

In both the OpenAPI specification and Huma's comments, the OperationID is described to be unique

The reason I haven't merged this myself is:

• It adds a field to the OpenAPI struct, something I'm wary of doing (see Implement RejectUnknownQueryParameters (Fix #660) #925)
• I agree with @rhodeon that this should be the default behaviour, considering the OpenAPI specification marks it as such

Would appreciate your review when you have the time @danielgtaylor!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.67%. Comparing base (0279842) to head (0a541af).
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #937      +/-   ##
==========================================
+ Coverage   92.52%   92.67%   +0.14%     
==========================================
  Files          23       23              
  Lines        4471     4557      +86     
==========================================
+ Hits         4137     4223      +86     
  Misses        275      275              
  Partials       59       59              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[danielgtaylor]

@wolveix I agree that this should probably just be default behavior. I'm not concerned with breaking people on this one as their generated clients will already be broken if they use duplicate operation IDs. Happy to call this a bug fix!