fix: fast exits

[troggy]

Requires leapdao/leap-core#164

Server-side of exit market maker had changed long time ago and bridge UI wasn't adapted yet. Addressing it here

Deployed on testnet.leapdao.org

• fallback to first validator data, if there is no period data found in the node
• use correct market maker endpoint for testnet
• use updated market maker API (v2, live for 7 months already 🤦‍♂️)
• use mobx's autorun to handle pendingFastExits persistence https://github.com/leapdao/bridge-ui/pull/258/files#diff-7dc47a481bab9d396bdfdc2da057b3c5R78
• fix: use utxoId for indexing pending fast exits, not tx hash (breaks when exiting outputs of the same tx) https://github.com/leapdao/bridge-ui/pull/258/files#diff-8bdbb99e41bebab451fe4b0fb076727fR108
• show initialized fast exits in the list until they finalized (payed out)

[troggy]

Test with:

# in leap-core
git checkout feat/fast-exit-return-signed-transfer
yarn
yarn link

# in bridge-ui
git checkout fix/fast-exits
yarn
yarn link leap-core
CONFIG=testnet yarn start

[MaxStalker]

Steps I took during review:

• Checked the code to my best ability and understanding
• Launched local version of bridge and initiated exit of 0.001 LEAP
• pendingFastExits in localStorage is populated with transaction and Unspent list also shows new status for that UTXO
• Succesfully exited 0.001 LEAP 🎉

Notes:

• there were some hiccups with bringing bridge-ui up locally on Windows machine
• I was able to get CONFIG_NAME populated, when I update webpack portion of val-loader rule to:

      {
        test: require.resolve('./src/config/env.js'),
        use: [
          {
            loader: 'val-loader',
            options: {
              CONFIG_NAME: process.env.CONFIG,
            },
          },
        ],
      },

and start:testnet script in package.json to:

    "start:testnet": "set CONFIG=testnet && yarn start",

Though this is specific case for Windows. If we want to support this platform, I would recommend that we opt to use cross-env module in the future