Create Navigation mechanism for wizard type flows

[J-Son89]

In the wallet designs there are multiple flows which have optional steps depending on the entry point to the flow.
These steps being optional are depending on whether or not the value has been collected or not.

In the case of Wallet, this includes Sending Assets, Bridging and sending Collectibles.

In the case of Sending an Asset here are some example variants for the flow:

Overall the send flow is this:

->select account to send from 
-> select address to send to 
-> select asset or collectible to send 
-> select input amount and routes etc
-> confirm transaction

On the home page of the wallet we can long press an asset or collectible to send
The flow then becomes

->select account to send from 
-> select address to send to 
-> select asset or collectible to send 
-> select input amount and routes etc
-> confirm transaction

On a given wallet account we can press the send call to action button
The flow then becomes

->select account to send from - 
-> select address to send to 
-> select asset or collectible to send 
-> select input amount and routes etc
-> confirm transaction

On a given wallet account we can long press the asset or collectible to send
The flow then becomes:

->select account to send from 
-> select address to send to 
-> select asset or collectible to send 
-> select input amount and routes etc
-> confirm transaction

From the generic scanner we can enter the send flow:
The flow then becomes:

->select account to send from 
-> select address to send to 
-> select asset or collectible to send 
-> select input amount and routes etc
-> confirm transaction

In the case of the wallet this data is available immediately from the beginning of the flow however the solution should also future proof incase that information is collected mid flow.

some suggested structures to follow are:

(defn flow-config [
  {
  :screen-id :screen/wallet.send-from
  :skip-step :from
  }
  {
    :screen-id :screen/wallet.send-to
    :skip-step :to
  }
  {
  :screen-id :screen/wallet.select-asset
  :skip-step :asset
  }
  {
    :screen-id :screen/wallet.input-amount
  }
  {
    :screen-id :screen/wallet.confirm-transactions
  }
])

(defn next-screen
  [flow-config current-screen skip-values]
  ;; iterate through flow-config and return the next screen-id where :skip-step is not on skip-values)

Most likely we need to add a solution to re-frame for handling this navigation sequence.
Add some lightweight tests to this, component spec or cljs tests.

These types of flow should also provide information available that are accessible on various steps of the flow.
For example the step index, that way we can know whether on the first or last step of the flow etc.