Add workaround for Swagger UI operation id wrapping

[cremor]

The issue or feature being addressed

Since Swashbuckle 6.6.0 updated from Swagger UI version 4.15.5 to 5.17.9 the operation ids (which are shown if app.UseSwaggerUI(c => c.DisplayOperationId()); is used) are wrapping even if there would be enough space. See swagger-api/swagger-ui#9577

Details on the issue fix or feature implementation

The workaround works, but I'm not sure if this is the best way to fix this. This is also why I didn't create a PR for Swagger UI directly.

I'm also not sure if this should really be added to Swashbuckle. But the index.html file already contains some other workarounds, so I guess it's fine?

I've tested the fix by using the SwaggerUIOptions.HeadContent property. But I'd like to test it with a real Swashbuckle package too. Is there a way to get a PR build published on the MyGet feed?

An alternative would be to modify the method DisplayOperationId instead. In there we could do this:

var builder = new StringBuilder(options.HeadContent);
builder.AppendLine("<style>.opblock-summary-operation-id { word-break: normal !important; }</style>");
options.HeadContent = builder.ToString();

I'm open for better ideas.

[martincostello]

Thanks for the suggestion, but as you noted I don't think this is a workaround we should build in and ship ourselves. Custom CSS can already be specified, so anyone affected by this could apply the workaround in their own code until it's fixed in Swagger UI itself.