Implement Oauth2.0 in Trino and refactor Trino controllers

[rohank07]

Configure to enable OAuth 2.0 authentication over HTTPS for the Web UI, python-client and Trino CLI
Ref: https://trino.io/docs/current/security/oauth2.html

• Configure Oauth2.0 https://github.com/StatCan/aaw-trino/commit/29a1e261df0b7fa6ea5070439933e2d7ca215641
• Refactor Trino controller StatCan/aaw-kubeflow-profiles-controller@0aeb5b2
• Refactor Schema controller StatCan/aaw-kubeflow-profiles-controller@0aeb5b2
• Update lsddp rules file

[rohank07]

Trino is now configured using Oauth2.0 and JWT auth. JWT is configured for the Trino schema controller to be able to create schemas for profiles. An admin (user: Rohan Katkar) is able to pass in its JWT token to the Authorization header in the REST API call to authenticate.

On the trino side only the admin's JWT token can be read. This is configured via the user-mapping file http-server.authentication.jwt.user-mapping.file=/etc/mapping/user-mapping.json

user-mapping.json: | { "rules": [ { "pattern": "^system:serviceaccount:([^:]+):default$", "user": "Rohan Katkar" } ] }