[Multi-Tenant] `backend` Admin Tenant API

[njlie]

Add the following to backend Admin GraphQL API:

type Query {
  tenant(id: string!): Tenant
  tenants: TenantsConnection! // pagination query for tenants
  whoAmI: { id, isOperator }
}

type Mutation {
  createTenant(input: CreateTenantInput): CreateTenantMutationResponse!
  updateTenant(input: UpdateTenantInput): UpdateTenantMutationResponse!
  deleteTenant(input: DeleteTenantInput): DeleteTenantMutationResponse!
}

• tenant query
• "who am I" query
• tenants query
• createTenant mutation
• updateTenant mutation
• deleteTenant mutation

Prerequisites

• [Multi-Tenant] backend tenant service #3123

[mkurapov]

Deleting tenant - I'm guessing we can only do this if there are no other resources that have been created under the same tenant, correct? Under foreign key constaints

[njlie]

Deleting tenant - I'm guessing we can only do this if there are no other resources that have been created under the same tenant, correct? Under foreign key constaints

Come to think of it, deactivation or some kind of soft deletion makes more sense.

[mkurapov]

After a discussion, we've realized that we need some sort of resolver that allows us to check whether the tenant making the request is an operator or not. This will allow us to show different UI elements based on whether the operator is a tenant or not.