Support bypass jwt on authorization header?
Internal conversation: https://huggingface.slack.com/archives/C04L6P8KNQ5/p1678874819105149?thread_ts=1678874751.420079&cid=C04L6P8KNQ5

The `x-api-key` header does not describe very well that it should contain a JWT, and it's not standard.

Maybe support passing the authentication bypass JWT (#898) via the `authorization` header instead.

As the `authorization` header is already used with Hub users/app tokens, we could check if the token starts with `hf_` to discriminate:
- Hub token: `Authorization: Bearer hf_app_abcdef...`
- JWT: `Authorization: Bearer aaaabbbb...`

Another option: a prefix such as `jwt:` could be appended to the JWT: `Authorization: Bearer jwt:aaaabbbb...`


Support bypass jwt on authorization header?: Internal conversation: https://huggingface.slack.com/archives/C04L6P8KNQ5/p1678874819105149?thread_ts=1678874751.420079&cid=C04L6P8KNQ5

The `x-api-key` header does not describe very well that it should contain a JWT, and it's not standard.

Maybe support passing the authentication bypass JWT (#898) via the `authorization` header instead.

As the `authorization` header is already used with Hub users/app tokens, we could check if the token starts with `hf_` to discriminate:
- Hub token: `Authorization: Bearer hf_app_abcdef...`
- JWT: `Authorization: Bearer aaaabbbb...`

Another option: a prefix such as `jwt:` could be appended to the JWT: `Authorization: Bearer jwt:aaaabbbb...`

