Creating additional tables in the view service for recording extended transaction data.

[aubrika]

We want to: ensure that view service has tables which maintain all of the plaintext values that the view service has ever seen

We want this because: then we can do queries on all data that the view service has the ability to decrypt.

What is that data? The encrypted components of a transaction:

• There will be an encrypted note per NotePayload in each Output, some sent to us, some sent to others
• The MemoCiphertext field will be moved to transaction level in lift Memo to transaction level #1222
• Support SwapPlaintext in the View service #1297 will introduce Swap plaintexts

We want a notes table that will record any note regardless of whether we control it. Once we have this, we can deduplicate fields in the existing spendable and quarantined notes tables, and when recording extending transaction data we can also add outgoing notes which we decrypt with our OVK.

To be able to make queries about transactions, we need a way to link these note plaintexts back to transactions - so we may need to introduce tables allowing us to determine which nullifiers were linked to which transactions, and which note commitments were produced by which transactions. (Tx_by_nullifier exists, no linkage yet between commitment and tx)

[aubrika]

This depends on the work in #1368