* fix: added client-side validation for challenge prizes
This commit aims to solve the issue #11765 by adding client-side
validation for the challenge prize. This way, a user is unable to create
a challenge if the prize is higher than what they can afford. Also, the
loading property is reset to false after fetching the challenge, however
this won't work if the request isn't successful.
* style: make validation conditional clearer
* fix: add exception handling when doing server requests.
This commit adds a basic try/catch block for handling server-side
errors, and successfully enables the submit button if something failed.
This may also fix#11545, in which a server-side error, difficult to
valide from the client, was causing the submit button to stay disabled
until reload.
* fix: reenable prize validation
* fix: bad indentation
* fix: Enable submit button on input change
* fix: add throttling to enableSubmit event.
* fix: reenable prize client-side validation.
Description: Use of a same object property group for differents types between a
challenge and workingChallenge
workingChallenge use group as and id but this.challenge have a group
object
Fix: Wait for server response for challenge edit. Set this.challenge
from response and not directly from form data workingChallenge
