Allow license tokens that start with airgap_

[rafpaf]

Accept license tokens with an airgap_ prefix, besides the already accepted 64-character long tokens.

This weakens the validation in the FE. Rigorous validation of tokens beginning with airgap_ occurs in the BE. See this Slack message.

[rafpaf]

• Allow license tokens that start with airgap_ #42733 👈
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rafpaf and the rest of your teammates on Graphite

[github-actions]

Codenotify: Notifying subscribers in CODENOTIFY files for diff 4a6dfe4...92e29e2.

Notify	File(s)
@ranquild	frontend/src/metabase/setup/components/LicenseTokenStep/LicenseTokenForm.tsx frontend/src/metabase/setup/components/LicenseTokenStep/constants.tsx frontend/src/metabase/setup/components/LicenseTokenStep/constants.unit.spec.tsx frontend/src/metabase/setup/tests/enterprise.unit.spec.tsx

[graphite-app]

Graphite Automations

"Notify author when CI fails" took an action on this PR • (05/16/24)

1 teammate was notified to this PR based on Raphael Krut-Landau's automation.

"Don't backport" took an action on this PR • (05/16/24)

1 label was added and 1 reviewer was added to this PR based on Raphael Krut-Landau's automation.

[replay-io]

Status	Complete ↗︎
Commit	92e29e2
Results	⚠️ 3 Flaky ✅ 2506 Passed

[escherize]

I double checked, and this has the expected behavior.

I was able to send the response, and the server was able to check it:

App started with:

MB_DB_CONNECTION_URI=postgres://bcm:password@localhost:5432/metabase_new
MB_EDITION=ee

[github-actions]

@rafpaf Did you forget to add a milestone to the issue for this PR? When and where should I add a milestone?