feat(authorization): add bearer token authorization

[nithinssabu]

Description of the change

Closes #276

Type of change

• [ ] Bug fix
• [x] New feature
• [ ] Breaking change
• [ ] Documentation update

Checklist

• [x] I have read the CONTRIBUTING doc
• [x] I have opened this pull request against the alpha branch
• [x] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation (if appropriate)

Further comments

[If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...]

[jwulf]

Hi @nithinssabu , thanks for the contribution.

Can you give me an idea of the use case for this?

[nithinssabu]

Hi @nithinssabu , thanks for the contribution.

Can you give me an idea of the use case for this?

Hey @jwulf

This is required as part of a change in the deployment functionality within Web Modeler. The epic is about unifying the deployment experience between the SaaS and Self-Managed product contexts.

In SaaS, deployments are easy from Web Modeler. Users select a cluster and deploy. We want to bring the same experience also to Self-Managed (currently users fill out a manual entry form where they have to enter the cluster details including the credentials).

This change is relevant for the authorization slice of the epic where we will switch to using the user token instead of the M2M token generated using client ID and secret.

In short, it's about changing from this:

to this:

PS: I was planning to reach out to you today. I just wanted to try this out first to verify if it works. I will read the contribution guide and improve the PR, add tests, fill more details, etc. before marking it as ready. In the meantime, if you already find any red flags or possible improvements in the approach, please share.