Bug/fix operation summary responsiveness

[klm-turing]

Make the Swagger operation summary component responsive and smooth

Description

This PR does the following:

Ensure that the “copy” button is displayed correctly, smoothly, efficiently and does not shrink the texts of the other elements.
Ensure that the operation method is correctly positioned so that the texts of the other elements are legible.
Remove wrong styles in the operation summary container.

Motivation and Context

Resolves #8940 and potentially closes #9980

How Has This Been Tested?

I tested these style changes with different screen sizes and make sure that all existing tests pass.

Screenshots (if appropriate):

Operation summary before changes

operation_summary_before.mp4

Operation summary after changes

operation_summary_after.mp4

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.

[klm-turing]

@char0n Thanks for taking a look. This one addresses summary operation responsiveness

I'll be submitting other small PR addressing the issue piece by piece as you suggest.