Get ready for mainnet flux deployment

[stevieraykatz]

Explanation of the solution

• Added a new shell script which allows us to fork an arg-provided chain (rather than hardcoded to mumbai)
• Made a slight tweak to Ethereum mainnet rpc url in .env to match the other url patterns
• Made generic deploy script flows for both Vaults and Strategies
• Removed unused/deprecated tasks from ...tasks/deploy/integrations
• Added steps to side-chain deployment task for managing registrar

Instructions on making this work

• run yarn or yarn install to install npm dependencies

[linear]

AP-786 Deploy Flux Strategy

This involves a number of steps:

• Deploy a testnet strategy/vault pair
• Run deploySideChain on Ethereum mainnet
• Deploy the Flux strategy contracts
• Configure the registrars (see AP-638)

[SovereignAndrey]

@stevieraykatz Seeming how vaults are setup now on testnet, do you think this PR is ready for a review?
PS. Looks like there's some merge conflicts to address with master branch.

[0xNeshi]

The only important comment is the "set strategy params in (Local)Registrar" one, see #384 (comment)

[0xNeshi]

Ah, there's a gotcha here - stratConfig parameter actually expects the name of the strategy config to use, defined as key of allStrategyConfigs (available values in this PR: dummy, flux).
See setStratParams task source for more details.

The task uses an internal converter (see cliTypes.stratConfig) to convert the stratConfig name into the StratConfig type and fills its data from allStrategyConfigs.

This may be counter-intuitive because the task's arguments are defined as:

type TaskArgs = {
  stratConfig: StratConfig; // CLI expects "string", but before running the task it converts it into `StratConfig`
  modifyExisting: boolean;
  apTeamSignerPkey?: string;
};

Is this too counter-intuitive? We could simplify this, the change(s) wouldn't be big.

Anyway, what needs to be done no matter how this task is called is that writeStrategyAddresses is called before it (the task), so that correct values are read within it.

  // Store addresses
  writeStrategyAddresses(strategyName, {
    locked: Locked.contract.address,
    liquid: Liquid.contract.address,
    strategy: Strategy.contract.address,
  });
  
  // establish registrar config on primary chain and this chain
  await hre.run("manage:registrar:setStratParams", {
    stratConfig: strategyName,
    modifyExisting: true,
    apTeamSignerPkey: signerPkey,
  });

[stevieraykatz]

Oh that's a poorly named argument. I'll switch the order and rename that arg then.