CCP-2921: Change Embed/Webcomponent Auth Header

[usingtechnology]

Description

For embedded webcomponents, do not use Authorization Bearer headers. Change to a custom header and allow pass-through of headers from the host application. These pass-through headers may include an Authorization Bearer header.

Since we haven't use gateway service and runtime-auth middleware outside of webcomponents, there is no change to core functionality. Documentation on tech docs and communication with any interested parties that are currently previewing embedded functionality will need to be informed of the header change.

Type of Change

feat (a new feature)

This is a breaking change because ... it may break the devcontainer? i moved to a mac silicon and the architecture is completely different so i had to add conditionals in the docker image and devcontainer.json

Checklist

• I have read the CONTRIBUTING doc
• I have checked that unit tests pass locally with my changes
• I have run the npm script lint on the frontend and backend
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• I have approval from the product owner for the contribution in this pull request

Further comments

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Release f08fb9e deployed at https://chefs-dev.apps.silver.devops.gov.bc.ca/pr-1787