Handle `ext.cattle.io.tokens` not being generically stable

[richard-cox]

Setup

• Rancher version: 2.14.0

Describe the bug

• Power API Keys list with new ext.cattle.io.tokens #12332 brought in management of the new public api token
• It's been discovered this isn't ready for use everywhere - Migrate login to /v1-public endpoint terraform-provider-rancher2#1998
• It's unclear where else is not ready to use
• The decision was taken to not ship this change in 2.14.0 or 2.15.0 and wait for confirmation

Additional context

[richard-cox]

/backport v2.14.0

[richard-cox]

Validation - New functionality has been removed, old functionality worked as before

@yonasberhe23 had a really good test plan for the new functionality, something similar would work but just going back to the old functionality. I've done a super quick version below

• List – Data source - Only loads data from /v3/tokens and not /v1/ext.cattle.io.tokens
• List – Data source - SSP / Vai does not come into play now
• Create – Norman API - via /v3/token and not /v1/ext.cattle.io.tokens
• Create – TTL / Max - setting to 90 days results in token with a TTL / Expires of 89
• Create – TTL / Custom - setting to 91 days results in token with a TTL / Expires of 1.5 hours
• Create – TTL / Custom - setting to 0 days results in token with a TTL / Expires of 89
• Create – TTL / Custom - setting to 10 days results in token with a TTL / Expires of 9
• Create – Scope - setting a scope displays the management.cattle.io.cluster id (not human name) of the targeted cluster
• Delete - Norman API - via /v3/token and not /v1/ext.cattle.io.tokens
• Create - Bulk - Row action + bulk work as expected
• Permissions - (i thought all users have CRUD on /v3/tokens)
• Table – Headers - state, acceess key, description, scope, ;ast used, expires, age
• Token validation - use token in curl request