fix:<meta name="referrer" content="no-referrer" /> inserted in HTML

[Mathias02]

Swagger UI -v 5.20.1 doesn't use csp for the "unsafe-eval" to be added

Description

Swagger UI version 5.20.1 doesn't use csp for unsafe-eval to be added, however, I added in dist/index.html to tell the browser not to send the Referer header at all when navigating away from the page.

Motivation and Context

This change is required to avoid Referer heade be sent to other pages when navigating away.

Close #7540

How Has This Been Tested?

I added svg tags in the HTML to see how these would be blocked for lack of unsafe-eval but nothing was blocked

Screenshots (if appropriate):

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.