fix: it aint over till its over streaming swaps completion

[woodenfurniture]

Description

In #7371, and issue was reported where streaming swaps UI were progressed to "trade complete" when streaming is still in progress (see #7371 (comment)). This PR addresses that.

Root causes:

• We were using a deprecated field swap_finalised to trigger completion state, which is not valid
• Our API wasn't able to find completed txs, resulting in reliance on the above field to complete trades (see https://api.thorchain.shapeshift.com/api/v1/tx/0x72A85E5F9F7FE723BF768FA0012AF0F1E25F206285679970F4A160037C4A50B1 for example)

Solutions:

• Rewrite trade status logic to treat all stages reported by the thornode API as Pending. This prevents convoluted logic returning Confirmed state when tx is still being streamed.
• Use thornode tx/{hash} endpoint to determine completed status for all thorchain swapper txs. This works for both streaming and non-streaming txs.

Notable changes:

• status bar will have "indeterminate" stripes while the streaming status is being initialized (isntead of sitting at 100% green), which is more conventional ux
• Minor updates to thorchain tx status copy

Issue (if applicable)

closes #7371

Risk

High Risk PRs Require 2 approvals

Moderate risk. This solves an issue with UI displaying the status of tx execution and does not affect user funds or ability for users to complete trades.

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

THORChain swapper, both streaming and non-streaming swaps.

Testing

• Can perform regular trades with thorchain swapper (all chains)
• Can perform streaming swaps from RUNE
• Can perform streaming swaps to RUNE
• Can perform streaming swaps from non-RUNE to non-RUNE

Engineering

Operations

• 🏁 My feature is behind a flag and doesn't require operations testing (yet)

Screenshots (if applicable)

With outbound tx (buy asset not RUNE)
https://jam.dev/c/b9660984-a567-46bc-ba6f-e9e037d07037

Without outbound tx (buy asset is RUNE)
https://jam.dev/c/99c865a0-df13-47dd-87fc-568de47323b7

Regular trade (no streaming)
https://jam.dev/c/f64594e2-0d96-44a6-8106-b9586831fa5b

[gomesalexandre]

Killer PR ser. Tested locally against develop, noticed one regression WRT "inbound Tx pending" state missing, which is more obvious with slow L1s (e.g UTXOs) but is happening both with RUNE and L1s ad inbound Txs.

Unable to test actual streaming swaps here, but logic looks sane to me and honours THOR docs, so happy to have ops test the streaming case (which has been confirmed working with two swaps/Jams in this PR) after this smolish regression is fixed 🙏🏽

• DOGE -> RUNE (no outbound Tx)

https://jam.dev/c/a002e844-8036-4cd0-9214-2882e72bb25e

While swap status detection was happy after inbound, noticed we're now missing the inbound pending state i.e this guy:

• RUNE -> DOGE (no L1 inbound, this is happening directly in THOR)

https://jam.dev/c/01261386-4242-4f62-9177-75b36b230c5d

Ditto, happy against develop except for inbound pending state missing

• Streaming swap: unable to test, will defer to @shapeshift/operations

[gomesalexandre]

Retested locally, still noting the same issue re: "Inbound transaction pending" missed until L1 Tx is confirmed and observed.

However, all next stages perform as expected - to be retested and stamped with actual streaming swaps once fixed after getting the Foxcrypt'd seed back again

RUNE -> DOGE (non-streaming) 🚫

https://jam.dev/c/c8716f58-ba79-4764-9613-6a9f4525326e

• Still seeing "Inbound transaction pending" missing here, though not super visible with RUNE as it's pretty fast and goes to the first stage of akschual polling in a few seconds

ETH -> DOGE (non-streaming) 🚫

https://jam.dev/c/c22ea5d7-1627-4436-9e95-919fb4f0edfb

• Same issue as above

DOGE -> RUNE (fake streaming of sorts i.e low amount but streaming swap) 🚫

https://jam.dev/c/688463cf-5814-400e-99fd-3db91d653765

• Same issue here
• Also noticing "Swap Status" does stay indeterminate after completion, see screenshots of swap pending vs. completion
  
  

[gomesalexandre]

Tested streaming swaps locally:

• RUNE -> FOX

https://jam.dev/c/c210100a-c6f3-49ad-b54e-10cf4b82bfeb

• FOX -> RUNE

https://jam.dev/c/2541cac8-c010-41cb-832d-d3efaa2ae030

Confirmed this guy does what it says on the box!

• The spotted issue re: "fake swaps" having indeterminate progress bar is a non-blocker and can be tackled in a follow-up if we want to, though definitely edge-case.
• Also non-blocking, as can be seen on the first jam at around 1:17, seeing some "Outbound transaction scheduled" but 1 out of 2 swaps which sounds off, and we should probably tackle as a follow-up i.e if outbound is scheduled, streaming is complete