Resolve "JWT API token support for Terraform Module Registry"

What does this MR do?

Adds a generic Gitlab::JWTToken and adds deploy_token_from_jwt, job_token_from_jwt, and personal_access_token_from_jwt token types to Gitlab::APIAuthentication along with a token_param location in order to support authenticating using JWT tokens passed as URL query string parameters, which is needed by the Terraform Module Registry work ongoing in !55018 (merged).

This allows you to authenticate an API endpoint in this manner:

authenticate_with do |accept|
  accept.token_types(:deploy_token_from_jwt, :job_token_from_jwt, :personal_access_token_from_jwt).sent_through(:token_param)
end

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • [-] I have included a changelog entry.
  • I have not included a changelog entry because this is a developer-facing change and does not require one.
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #324237 (closed)