Crypto-to-fiat: Resolve edge cases with liquidation addresses

[jakubcolony]

Description

See issue #2793 for details.

This PR resolves a number of potential issues with liquidation addresses:

1. Check KYC handler was checking for existence of any liquidation address, instead of one linked to the user's bank account. If it doesn't exist, it will create one.
2. When updating bank account details, a new bank account is created
   1. For accounts with the same currency, the existing liquidation address needed to be updated with the new account ID.
   2. For accounts with different currencies, a new liquidation address should be created.
3. As there can be multiple liquidation addresses that can change at any point (primarily when user updates their bank details), we cannot rely on the ones stored in our DB. For that, a new query was added to get liquidation address for a given user.

It also removes the bridgeXYZQuery lambda, as handling both queries and mutations in a single lambda allows for less code duplication and easier deployments.

Note: In this PR I'm also testing the possibility of splitting amplify schema into multiple files in hope to make it more manageable, considering the existing schema is already nearly 4k lines long.

Testing

Restart your dev env - otherwise the separate schemas will not get picked up.

Issue 1:

1. Make sure you set the Posthog and Persona env variables and run npm run prepare.
2. Start KYC flow (you don't need to finish it though).
3. Add USD bank account details (EUR accounts can't be tested in sandbox). You will also need to use a US address.

On next refetch the CheckKYCStatus query should return a liquidation address.

Issue 2:

1. Update bank details to another USD account.
2. Check that the liquidation address is still the same.

In production, if you updated bank details to EUR account, new liquidation address should be created. In sandbox however we can't really test subpoint 2).

Issue 3

You can run the following query with your user address to confirm it returns the liquidation address:

query LiqAdd {
  bridgeGetUserLiquidationAddress(userAddress: "")
}

Resolves #2793

[rdig]

When trying to test this, loading the Crypto to fiat user profile tab, the bridgeXYZMutation crashes

So the KYC button doesn't show up:

I have all the env vars properly set, and have ran npm run prepare (I've also tried setting the apiKey inside the bridgeXYZMutation to the sandbox key, but still no change)

[jakubcolony]

@rdig looks like the import path was off, the joys of vanilla JS development 😃

[rdig]

I keep running into issues. Sorry about that :(

I'm attempting to start the KYC process, but the mutation lambda errors out

Note that as far as I'm aware the sendbox key and url are correctly set:

[jakubcolony]

@rdig I wondered if it's because of the obviously fake email you used but even with the same details, it works fine on my end. I am also connected to the sandbox API with the same key.

Screen.Recording.2024-08-06.at.23.25.32.mov

Let's catch up on this tomorrow

[rdig]

Yeah, it's possible I'm doing something wrong with my setup.

[rumzledz]

Hey @rdig just chiming in -- I've seen this happen to me when I came from a branch that had a different network hash. Just thought I'd double check if you've restarted your dev again on this branch? But knowing you, you probably already have!

[rdig]

As I remember yes, I rand this fresh, but if there are any doubts I can test again just to make sure my findings are not faulty

[rumzledz]

I've stuck with using a US address and a US bank account all seems to be working @jakubcolony ✨

I can prove that I updated it because the id field of the bankAccount object has been updated yet the liquidationAddress remained the same 👌

[rdig]

Re-tested this (live, with @jakubcolony), with proper US and EUR accounts and not it's working as expected.