[Multi-Tenant] Tenanted Assets

[njlie]

Because assets aren't associated with a Wallet Address like Open Payments resources are, it becomes necessary to add a tenantId to them to determine which tenant that asset belongs to.

• Add required tenantId column to assets table
• Acquire tenantId from request header and pass into asset service logic during graphql requests
• Add tenantId to database queries on assets

Prerequisites:

• [Multi-Tenant] backend tenants table #3103
• [Multi-Tenant] Use http-signatures to determine tenant identity during requests #2928

[njlie]

Closing as the new design for Multi-Tenancy no longer uses logical barriers for tenanted resources.

[mkurapov]

@njlie re-posting my comment from the planning doc:

If we want to have assets be tenanted, we need to change how we create asset liquidity and settlement accounts.

Currently, when we create an account in TB, we use the auto-incrementing ledger value (smallint in PSQL) as the id for the asset settlement account. If we were to create an asset for a second tenant (in a separate schema/db), the settlement account creation would fail because of the id collision.

One way to solve this would be to just start storing liquidityAccountId and settlementAccountId on the assets table, or something in a different lookup table

[mkurapov]

@njlie going to take this one on and come up with some solutions to the question of liquidity & settlement accounts