fix: refacto react-hook-form logic for roles based organizations

[clegirar]

Start a refacto about react-hook-form logic for roles based organizations.
The goal is to understand better the react-hook-form flow because it's a lot of abstractions. You can give your opinion if you find it more appropriate and understandable.

TODO:

• Re-check naming, especially for zod objects and types
• Re-check logic
• Test the process a lot

Can't refacto ConfigureVotingFormData and OrganizationData because it's generic between all organizations, but could be cool to adapt it.

[netlify]

✅ Deploy Preview for teritori-dapp ready!

Name	Link
🔨 Latest commit	e63f410
🔍 Latest deploy log	https://app.netlify.com/sites/teritori-dapp/deploys/67b243ccc1f5b200095a1031
😎 Deploy Preview	https://deploy-preview-1471--teritori-dapp.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for gno-dapp ready!

Name	Link
🔨 Latest commit	e63f410
🔍 Latest deploy log	https://app.netlify.com/sites/gno-dapp/deploys/67b243cc24670c0008e5e6b8
😎 Deploy Preview	https://deploy-preview-1471--gno-dapp.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[WaDadidou]

Would be better to do that now, no ?

[WaDadidou]

Hello, I've added a custom error message to min(1) usages to avoid differences between:
"submits with no value in field"

and
"writes value and deletes written value in field"

I also changed the value for DEFAULT_FORM_ERRORS.required to have the same error as default RHF's "required" error.
So, we have now only one error message for required fields: becomes

Commit: e63f410