scaffold lab api teams

[olivercodes]

Implement the teams api for DI platforms.

https://app.mural.co/t/twma7655/m/twma7655/1659125905811/89644c232bd59569a1103607f3b2fa263c1ed25e?sender=ue017dd0a0ba865be72d75848

Decided to start over from the old repo: https://github.com/ThoughtWorks-DPS/lab-api-teams-python-archive
And rebuild it using Golang. Advantages in doing so:

1. ability to export types and interfaces such that operator modules can import and reconcile the domain entities (example, these https://github.com/ThoughtWorks-DPS/lab-api-teams/blob/main/pkg/domain/teams.go can be imported by our Operators to use the same Struct models)
2. k8s standard to build in golang, multiple libraries and tools to support development (the lab-api-teams itself may never need to import a k8s library, however the operators subscribing to it will)
3. Go clean code patterns lend themselves well to the requirements of our api. Meaning, we will need to be able to run it on multiple clouds against multiple different databases, so that the api works on gcp, azure, and aws. To do this, we need to follow the Clean Architecture principles, and develop interfaces for our entity models so that each database type is just an interface implementation. Go lends itself well to this pattern

ACs:

1. Ability to GET/LIST/POST/PUT/DELETE teams. Detailed requirements for each endpoint in mural
2. Ability to GET/LIST/POST/PUT/DELETE namespace records. Detailed requirements for each endpoint in mural
3. Ability to GET/LIST/POST/PUT/DELETE gateway records. Detailed requirements for each endpoint in mural
4. Works with Redis for rapid local development
5. Works with DynamoDB for remote deployment
6. CircleCI setup and function al
7. Build passing and deploying to DPS labs clusters

There are additional endpoints documented in mural that are more specialized to some of the domain entities (for example, there's a GET endpoint for fetching only Master namespace records). We will tackle these specialized endpoints in a subsequent task.

[olivercodes]

from @ncheneweth - Assess whether DynamoDB is right choice. Could be a managed service backend (that's on the cluster, for example)

Everybody ships SQL, for example
Or POSTgres local to cluster, Mongo local cluster, etc.

OSS options as well

• TiKV / TiDB
• Vitess

[olivercodes]

Breaking this into multiple tasks: #3 #4 #5 #6 #7 #8

Completed ACs:
Ability to GET/LIST/POST/PUT/DELETE teams. Detailed requirements for each endpoint in mural
Ability to GET/LIST/POST/PUT/DELETE namespace records. Detailed requirements for each endpoint in mural
Works with Redis for rapid local development