AP-680 Limit what vault config update can change

[stevieraykatz]

Explanation of the solution

We allowed the setVaultConfig method to overwrite a number of fields that should be treated as immutable. There are now two structs:

• VaultConfig which is stored upon construction
• UpdateVaultConfig which is passed as an argument and only contains limited mutable fields:

  struct VaultConfigUpdate {
    address strategy;
    address registrar;
  }

Instructions on making this work

• run yarn or yarn install to install npm dependencies

[linear]

AP-680 Change "IVault.setVaultConfig" to only accept a subset of `VaultConfig` fields to update

As per ser Steve's comment:

Fair points re: these tokens and the Vault type being editable by config updates. Perhaps we should have a concept of config and a concept of constructorArgs and they should be separate. See longer winded answer about why these fields exist here in addition to in Strategy here: AngelProtocolFinance/ap-subgraph#21 (comment)

In short, the only fields that should be updateable are: registrar address, apTokenName and apTokenSymbol (andrey katzman please confirm). Field admin should probably be removed and the APVault_V1 contract made to inherit ~OwnableUpgradeable~ Ownable (see Andrey's comment below).

[SovereignAndrey]

Good call!