Initial project and component dashboards

[sra405]

Introduction of an admin dashboard for viewing and configuring editor projects. The initial purpose of this dashboard is to increase visibility of built projects and their current state. It also provides an easy interface to update aspects that didn't build correctly i.e. images.

Notes

Currently this utilises a similar approach to the badge-service however auth approaches aren't aligned with editor-api using token introspection only to get user info, this includes direct authentication in app. Currently:

• editor-api authenticates via a token set in the request headers set from a previous auth instance
• an admin dashboard requires direct authentication flows and have access to an auth object
• current apps and gems utilise one or the other but not both

Access to the dashboard (similarly to badge-service) utilises role assignments against the users rpf account. If they have editor-admin assigned to their account they're granted access to the dashboard, if not they can't go to /admin or any of its subpath.

Staging/Prod

Environment variables needed in staging/prod:

# to be added to staging
HYDRA_PUBLIC_URL=https://staging-auth-v1.raspberrypi.org
HYDRA_CLIENT_ID=editor-api-dev
HYDRA_CLIENT_SECRET=secret

IDENTITY_URL=https://staging-my.raspberrypi.org
HOST_URL=https://staging-editor-api.raspberrypi.org

# to be added to production
HYDRA_PUBLIC_URL=https://auth-v1.raspberrypi.org
HYDRA_CLIENT_ID=editor-api-dev
HYDRA_CLIENT_SECRET=secret

IDENTITY_URL=https://my.raspberrypi.org
HOST_URL=https://editor-api.raspberrypi.org

[sra405]

not needed with the CORP middleware now adding the required headers in prod

[sra405]

closed the wrong PR 🤦

[loiswells97]

Wahay, let's get this out there 🚀