Fixed authorization header remove logic

[malincrist]

Problem

The Authorization header is not correctly refreshed in test console. Its value is removed when selecting "No auth" and the Http Request is not updated accordingly.

Solution

1. If the authorization header is added as a separate header for the API and marked as required, it will not be removed when selecting "No auth".
   Its value will be removed and the HTTP Request will be updated accordingly.
   Users cannot remove this header.
   It is marked as required by the text "Value is required" under the input.

2. If If the authorization header is added as a separate header for the API and not marked as required, it will not be removed when selecting "No auth".
   Its value will be removed and the HTTP Request will be updated accordingly.
   Users can remove this header manually.

3. If the authorization header is not defined for the API, when a grant type is selected (eg: "implicit"), it will be added in the Headers section, and its value will be populated.
   When "No auth" is selected, the header will be removed and the HTTP Request will be updated accordingly.
   Users can remove this header manually.

The authorization header is always marked as secret: It will always be displayed with its value masked out and with the additional toggle button that provides the possibility to display its actual value.

Closes #1933

[github-actions]

Accessibility Insights Action: All applicable checks passed

• URLs: 13 URL(s) passed, and 0 were not scannable
• Rules: 28 check(s) passed, and 24 were not applicable
• Download the Accessibility Insights artifact to view the detailed results of these checks

---

This scan used axe-core 4.3.2 with Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36.