replace creation of tokens from Norman to Steve

[aalves08]

Summary

Fixes #12332

Occurred changes and/or fixed issues

• Replace creation of tokens from Norman to Steve

Technical notes summary

• moved headers to the actual template file since we now lose the configuration of headers for NORMAN.TOKEN because the table we will display is a mashup of both token types
• added UI option to set token as enabled or disabled when creating one
• in shell/models/ext.cattle.io.token.js had to define some new properties that at first glance my be reductant but they allow us to make it compatible with the old NORMAN.TOKEN headers so that table values for the new token are populated/displayed correctly
• incorporated new state inactive as now a new token can be enabled or disabled
• added banner to Account and API Keys page above the table with a deprecation notice IF there are old token entries displayed

Areas or cases that should be tested

Areas which could experience regressions

• option never only works if max TTL is set to < 0 (updated the UI accordingly, also with banner message to explain to user)

Screenshot/Video

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

[richard-cox]

Definitely worth updating the tests / regression test. Would also be good to show some examples on how to validate that the tokens work (if you create a token, copy any curl request the ui makes when logged in, change the url to just something somple like /v1/pods and swap in the auth bearer token we suggest).

We also might need to pivot on the message, i don't think the deprecation of v3/tokens has been announced. visually it might need to be "legacy" and we tone down the warning message

[richard-cox]

some tweaks required around deprecated + legacy, and some questions on the new max/ttl handling

[richard-cox]

This one needs a squash merge