"sync_exclude" flag for Spends and Outputs

[aubrika]

We want to be able to mark Spends/Outputs as not to be included in CompactBlocks after submission for high-volume applications, to make the view server more efficient on sync. We can do this by adding a new flag to Spends and Outputs, sync_exclude

To do this we can:

• [x] Add another map() to note_payloads in finalize_compact_block to filter out relevant payloads based on this flag

• [x] Modify Spend action to add the exclude flag

• [x] Modify SctManager:StateWrite:nullify to accept an additional argument to exclude from pending_nullifiers

• [ ] https://github.com/penumbra-zone/penumbra/issues/4407

• [ ] https://github.com/penumbra-zone/penumbra/issues/4408

• [ ] Set CompactBlock cost to 0 where sync_exclude is true

• [ ] Downstream the necessary modification side-effects to the web-side, if applicable

• Questions

  • Do we want to store the associated notes and nullifiers in the view service on submission to maintain a historical record on the originating instance? Or do we need to provide for this at all?
  • Do we want to provide a "full sync" option that includes the "sync_exclude" transactions? This would allow someone to opt-in to the less efficient but more complete behavior currently implemented in the view server.

[hdevalence]

We'll want to consider how this affects FMD (currently we have a rule of 1 clue per output, this should probably be 1 clue per sync included output, right?) and what the plan for syncing is, so we can be sure the feature works end to end.