Apply Dynamic cfg to p2 & p3 cases

[snadrus]

This builds atop PR #710 (which implemented P1 items) to implement P2 & P3 items of the following punchlist.
Logic fixes: forgot 'base' changes! Atomic where better.
New component: working with Dynamic[struct{...}] required a new approach.

Misc_Included_Commits
Better testing separation by guaranteeing different databases used.
SQL:

• NEW: an AFTER trigger switched to BEFORE + modifying NEW so there's no window of time for error.
• MOD: modified old code to help reapply work better. Should have no effect on fully-upgraded setups.

PunchList
The remaining items are P4-5 and "No need"

Subsystems

• XXMax P4, medium difficulty

Fees - all P2, easy, done
Addresses - all P1, hard, done
Proving - all, P4, easy
Http - no need
Market

• StorageMarketConfig
  -- MK12 - all here, P3, easy-ish, done
  -- MK2, P3, done
• IPNI - P4
• Indexing - P5, easy
• PieceLocator - P2, easy, done

Ingest - P1, done
Seal - No need
APIs->Chain - P2, medium-hard, done
Alerting - P3, easy, done
Batching - P2, easy, done

[snadrus]

I will add a test for the eth_client by moving money between wallets and back after a failover (how many lotus nodes, stop).