Do not count SV submissions in app activity recording

[meiersi-da]

Problem

A featured app creating a contract that is then archived by a transaction submitted by an SV node will create featured app activity twice for the featured app: once for the tx creating the contract, and once for the SV-submitted transaction archiving it.

The latter is problematic as there is no burn for an SV-submitted transaction.

Proposal

Do not count app activity for transactions submitted by SV-nodes.

Concretely:

1. Store DsoRules in RewardReferenceStore
2. Do not create app activity for submissions from participants whose participantId is in DsoRules.svs.
3. Bump the "code version" for app activity computation to avoid mismatches.

Discussion

FYI: @rautenrieth-da @dfordivam @adetokunbo