Fix: Add missing labels for crypto to fiat and refactor bridgeXYZMutation

[mmioana]

Description

This PR addresses multiple issues:

• the label shown for the 3rd column Routing number for USD accounts and BIC for EUR accounts
  
  

• the status pill and call-to-action default values if the retrieved kycStatus is null or empty
  

• improving the error handling when an invalid liquidation address is created by Bridge by using isAddress from ethers and returning a null value if the check is false

• aaaaand a bit of refactoring of the bridgeXYZMutation lambda

Testing

TODO: So let's also test these changes locally, though the focus on this PR review should be more related to the code refactoring.

• Step 1. Make sure you add .env files to the bridgeXYZMutation lambda

Important

It should have the following content - please ping me for the values if you don't already have them

BRIDGE_API_URL=
BRIDGE_API_KEY=
ENV=dev

• Step 2. Now connect as leela and go to http://localhost:9091/account/crypto-to-fiat
  

• Step 3. Enter the personal details, go to the next step, close the modal and refresh the page - you should be able to add you Bank details now
  

• Step 4. Add an USD account (you can use this https://randommer.io/routing-number-generator to generate some values, though the Routing number needs an extra digit)

• Step 5. Check that the Routing number column is displayed
  

• Step 6. Add an EUR account and now check the column label gets updated to BIC
  

• Step 7. Now if you check the amplify logs you'll see a message similar to

No liquidation address found for account, creating one
Newly created liquidation address <SOME_ADDRESS_HERE> is not valid

but the details still show up on the page, beside the liquidation address

• Step 8. Now if you refresh the page, a liquidation address should show up that was actually created on Bridge, but we didn't store it as it isn't a valid address

The thing is, on DEV, Bridge will generate liquidation addresses that are not considered to be valid - utils.isAddress will return false, hence this value will not be stored.
Before the changes on this PR, we directly called

      utils.getAddress(
        externalAccountLiquidationAddress,
      )

that threw an error in case of an invalid address, causing the UI to no longer display any information without a page refresh. Now this should be fixed, just that the liquidation address will not be displayed without a page refresh

• Step 9. Now in checkKYCHandler at line 32 add throw new Error() and refresh the page
• Step 10. You should see the following screen
  
  compared to master
  

Diffs

Changes 🏗

• bridgeXYZMutation lambda refactoring
• use utils.isAddress for checking the liquidation address before storing it

Resolves #3442
Resolves #3496

[jakubcolony]

We tested it together on a call against Bridge production and confirmed everything still works as expected, including:

• getting KYC status
• updating bank details
• drains history
• creating liquidation addresses

Nice refactoring effort, thank you for taking the time to make it look prettier 🎉

[jakubcolony]

Perhaps operations.js would be a better name, similarly to how it's called in domain balance lambdas?