Write contract config to vstorage

[LuqiPan]

What is the Problem Being Solved?

Description of the Design

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

[samsiegart]

In progress as in I'm working on figuring out the acceptance criteria with the team

[samsiegart]

We've decided that we just need to publish the feeConfig to vstorage under published.fastUsdc.feeConfig

? What config should the contract publish?
  :- terms
    - Denoms already published elsewhere
  :- oracles
    - UI doesn't need to know these
  :+ FeedConfig
    + OCW requires this
    . Already published under `published.fastUsdc.feedConfig`
  :+ Fee config
    + UI requires this
    ?! where to publish Fee config
      :+ `published.fastUsdc.feeConfig`
        + clear lookup
        - if we add more contract config we'll have more keys
        + determined/changed at a different time than other config
      : `published.fastUsdc`
        + natural home for info about the contract
        + can hold a JSON that has feeConfig and whatever else
          - if we serialize with plain JSON then it can't ever have remotables or bigints
          - if we serialize with CapData then reading the feeConfig is harder
            + we're providing a library anyway to read the fees
  :+ poolMetrics
    . Liquidity pool already writes this
  :~  SettlerAccount address
    + Needed by UI to determine noble fwd address
    ! Is SettlerAccount known in advance? Might not qualify as "config". Can probably publish separately.
  :~  PoolAccount address
    ? Why would we need to know this?
    ! Is PoolAccount known in advance? Might not qualify as "config". Can probably publish separately.