Hotfix - clean input after staking and updated title text

[jeremy-babylonlabs]

• Improved staking clear input logic
• updated staking and FP title text

[gbarkhatov]

@jeremy-babylonlabs Do we need to count the resets as state?

[jrwbabylonlab]

@jeremy-babylonlabs wouldn't this be easier with way less changes? #80

But will need ur guys help on testing this tho. it works for me

[vitsalis]

I don't understand why are we counting resets

[jrwbabylonlab]

I don't understand why are we counting resets

Because there are re-rending happening where the parent and child components (staking <-> stakingAmount) is affecting each other with their states and props being passed around. for example, setStakingAmountSat is changing the parent component's state which has a lot of dependencies on it, one of it is the state reset and it's being passed down into the child component.

Jeremy's solution is to a hack that try to fix another hack. It works, but u will see the counter actually incremented a lot (due to re-rendering issue in our code).

I proposed another solution #80 which will at least cut the reset dependency from setStakingAmountSat from the child component. But we are a long way to go from making the 3 components (staking, stakingFee, stakingAmount) to a more stable code. Right now, if u touch a single line of code in any of the 3 components, it affect a bunch of logic across whole staking components.

[jeremy-babylonlabs]

using a reset counter can make sure the states rerenders in the lifecycle. but agreed and going with @jrwbabylonlab's approach for now.

[gbarkhatov]

@jeremy-babylonlabs I suggest we do add strong to steps, so it's more emphasized for the end user (for both steps)

      <p>
        <strong>Step-1:</strong> Select a finaltiy provider
      </p> 

Other than that PR does what it should - resets the amount