Initial implementation of stake form

[kkosiorowska]

Closes #95

This PR adds a stake form. The data after approving the form will be saved in the context to use the given amount in a later step. The form for ustake and stake are very similar, so let's create a form base component. It will allow us to use it for unstake flow later. Changes:

• Added styles for the Tabs component
• Created the form base component
• Handling of the stake form
• Basic validation for form input
• Added necessary methods that convert numbers from floating point number to bigint

Screen.Recording.2023-12-29.at.09.07.37.mov

[kkosiorowska]

A minor comment: would be helpful to organize the formatting/converting logic to make the functions consistent and readable with each other. Let's do this in a separate PR - #101

[r-czajkowski]

Not sure about the name of this component because at first sight, it may indicate we can render any form but actually we are rendering stake/unstake form.

[kkosiorowska]

Yes, it's true this name isn't perfect. But I don't have a better idea. You are right, but on the other hand, we are just displaying the form there. The type of action restricts us on the types of form. If you just have any better idea let me know.

[r-czajkowski]

We need to figure out how to display the correct steps based on the form type. In this case, if a user changes tab to unstake, fills a form, and goes to the next step this component will display the next step for staking not unstaking. Just flagging, we probably should address it in a separate PR during the unstaking flow work.

[kkosiorowska]

Great catch! Let's do it as you say in a separate PR. We will have to think about it so I will also create a task to not lose it. #127

[r-czajkowski]