view: add support for auctions

[TalDerei]

Describe your changes

View server implementation for auction.

Issue ticket number and link

References #4251

Checklist before requesting a review

• If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

[TalDerei]

what's the utility of these action checks?

[erwanor]

On advice, we scan transactions and their actions, and record auction metadata by their asset id. This is useful to be able to display relevant asset metadata when presented with an asset id (among other things).

[hdevalence]

For a little bit more context: Values in the shielded pool are an Amount and an AssetId. The asset ID (an $\mathbb F_q$ value) is the currently always a hash of a denom string, and client tooling looks up asset.Metadata via the asset ID in an asset registry.

The chain maintains one minimal asset registry (just containing denoms), but this registry does not include entries for all of the LPNFTs (and now ANFTs), because this would bloat the chain state. Instead, the client's view service is responsible for locally deriving and caching the metadata of the bearer tokens it creates. This saves data for all the other clients, who don't want to have to maintain knowledge of everyone else's position NFTs.

[TalDerei]

I reviewed this earlier this morning on an outdated change-set, but haven't dived deeply into the storage.rs module.

[erwanor]

I think that this is ready for review, the discoverability / rendering of the commands needs to improve, but seem good enough for an mvp.

A few lines about the state modeling in the view server, this PR:

1. Adds an auctions table in the rust view server:

-- This table records the user's own auction state, using the
-- auction id as a primary key. An extra-column is available
-- to cross-reference note commitments that is associated with
-- the entry.
CREATE TABLE auctions (
     auction_id             BLOB PRIMARY KEY NOT NULL,
     auction_state          BIGINT NOT NULL,
     note_commitment        BLOB
);

2. The sync worker will record auction metadata as part of its block scanning routine (itself contingent on detecting activity)

3. As part of recording SNR asset data, it will update the auctions view state with an associated note commitment

4. This note commitment is used to cross reference spendable notes and cleartext notes from the spendable_notes and notes tables

[erwanor]

I have tested that I am able to:

• query my auction state
• go through the lifecycle of a DA: scheduling, terminating, and withdrawing

[erwanor]

Optimistically merging this, async reviews welcome