`deck file openapi2kong` creates multiple routes based on path parameter enum - need an opt-out

[harshadixit12]

deck file openapi2kong generates separate Kong routes for each header parameter combination when an OAS spec defines headers with both required: true and enum values. There is currently no CLI flag or OAS annotation to suppress this behaviour.
Customers who cannot modify their OAS specs — because those specs feed external API catalogs shared with third-party consumers — have no way to restore the original single-route output.