feat: add number input for finality window

[kstroobants]

Fixes #710

What

• Added a field to the frontend to change the finality window of the appeal process

Why

• To add more value to the user

Testing done

• Tested the new feature on the webpage

Decisions made

I have put the field below the leader. Let me know if it is better to put it in the settings tab.

Checks

• I have tested this code
• I have reviewed my own PR
• I have created an issue for this PR
• I have set a descriptive PR title compliant with conventional commits

Reviewing tips

See code changes and run the studio.

User facing release notes

A number field is added to the frontend to change the finality window of the appeal process.

[kstroobants]

@denishacquin Feel free to change the UI look.
@cristiam86 I don't know if this feature is good/bad for the online hosted studio. We should let Bulat know if he should disable access the the rpc method but then the field should also be disabled.

[kstroobants]

@cristiam86 I don't know if this feature is good/bad for the online hosted studio. We should let Bulat know if he should disable access the the rpc method but then the field should also be disabled.

Added check in frontend field based on VITE_IS_HOSTED so it won't be shown in the hosted version. @YeagerAI-Bulat When hosting we should write a meaningful finality window in the .env.example file.

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[github-actions]

🎉 This PR is included in version 0.29.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀