[Multi-Tenant] `backend` tenant service

[njlie]

The backend should provide a tenant service that other services can use to retrieve tenant information, given an id.

Pseudocode for Tenant service:

CreateOptions {
  publicName: string
  email: string
  apiSecret: string
  idpConsentUrl: string
  idpSecret: string
}

TenantService {
  create: (options: CreateOptions) => Tenant
  get: (id: string) => Tenant
  update(id: string, input: { ...tenantFields }
  delete: (id: string) => boolean
}

• Create TenantService and add it to IoC container
• create function
  • create function should call create tenant endpoint on auth server admin api
• get function
• update function
• delete function
  • delete function should call delete tenant endpoint on auth server admin api
  • use soft deletion

Prerequisites

• [Multi-Tenant] backend tenants table #3103
• [Multi-Tenant] auth tenants table #3113
• [Multi-Tenant] auth tenant service #3122

[koekiebox]

Could we also add caching to the tenant? Similar to what we did for walletAddress and asset?