UX improvements, #PG-5232

[lachiebol]

Description

• Improved wording for token popup
• Made try it out responses more clear by highlighting section
• Changed wording on authorise button
• Changed text on authorise button when connected
• Cleaned up example input CSS (better disabled field feel & standard backgrounds)

Issue No

Steps to Replicate the Issue

Checklist

• [✔/✖] Tested locally or on demo2/demo3?
• [✔/✖/NA] New test case added/updated?
• [✔/✖/NA] Are all newly added texts included via translation?
• [✔/✖/NA] Are text sanitized properly? (Eg use of v-text v/s v-html for vue)
• [✔/✖/NA] Version bumped?
• [✔/✖/NA] Documentation updated?

[AltamashShaikh]

@lachiebol LGTM overall, but this looks like a valid concern, can you check

High-Risk Issues Blocking

  Annotations/GlobalApiComponents.php:18 changes the OpenAPI security scheme id from MatomoToken to Matomo API token, and Annotations/GlobalApiComponents.php:36 uses the same spaced name as the
  component key. OpenAPI component keys are expected to be identifier-like keys, not user-facing labels with spaces. The fixture now contains "Matomo API token" under components.securitySchemes, so
  generated specs become invalid or at least less interoperable for validators/codegen tooling. Keep the scheme id stable, e.g. MatomoToken, and put the user-facing copy in description or UI-layer
  text.

[lachiebol]

@lachiebol LGTM overall, but this looks like a valid concern, can you check

High-Risk Issues Blocking

  Annotations/GlobalApiComponents.php:18 changes the OpenAPI security scheme id from MatomoToken to Matomo API token, and Annotations/GlobalApiComponents.php:36 uses the same spaced name as the
  component key. OpenAPI component keys are expected to be identifier-like keys, not user-facing labels with spaces. The fixture now contains "Matomo API token" under components.securitySchemes, so
  generated specs become invalid or at least less interoperable for validators/codegen tooling. Keep the scheme id stable, e.g. MatomoToken, and put the user-facing copy in description or UI-layer
  text.

I'll just revert this, I don't think it's impacting UX too much. The description change is probably enough here

[lachiebol]

@AltamashShaikh UI test fixed, failing backend test is the github issue not the tests