Add is_active column to nft_metadata table

[tifrel]

This PR

• Adds a is_active column to nft_metadata

Checklist:

• does a DB schema change
  • hasura permissions are updated
  • the indexer is halted
  • the corresponding minterop-producer PR is ready
  • the corresponding minterop-consumer PR is ready
• changes pubsub payloads
  • the indexer is halted
  • the corresponding minterop-producer PR is ready
  • the corresponding minterop-consumer PR is ready
• deprecates hasura permissions
  • frontend won't break
• creates hasura triggers/actions/events etc.
  • postgres DB user has been granted appropriate permissions

[bh2smith]

This PR does exactly what it says it does. I am just left wondering what is the intended purpose of adding it. Do we have some list of inactive tokens we would set to false immediately after this lands?

[tifrel]

This PR does exactly what it says it does. I am just left wondering what is the intended purpose of adding it. Do we have some list of inactive tokens we would set to false immediately after this lands?

Nope, we are deactivating old metadata on metadata updates for dynamic NFTs, such that we can query active metadata by their mb_internal_id = {ID} and is_active = true. Now there is an edge case of an update mechanism where we would set metadata to be inactive while it's actually still in use, and the only way to figure out is to join token count. If there are no more unburned tokens associated with a metadata, it is inactive, and I have implemented that logic when updating the field.

[bh2smith]

Easy peasy!