BUG: Missing translation on markdown validations

[Comoque1]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://dev-alkem.io/user/admin-alkemio/settings/account
2. Start process for template creation
3. On the dialog click on the markdown field
4. Click outside - validation error is shown, but is not translated

Expected behavior
There is MD validation error translation.

[reactoholic]

This task isn't straightforward because the current translation approach relies on a common hook that takes a key, which must match the key in the translation file.

Challenges:

Error Message Handling: We're passing the entire error message from Formik (e.g., "profile.description" is a required field), rather than just the key.
Key-Name Dependency: The name prop of the FormikMarkdownField component must align with the Yup structure used in Formik. Simply extracting keys from the full error message won't work, as it would result in a messy, top-level error message structure in the translation file—something we want to avoid.

Recommendations:

• Unify Error Messages: Create a ZenHub issue to standardize error messages across the application. Currently, there are three or more variations for the same type of error, which leads to inconsistency.
• Update Translation Logic: Create a ZenHub issue to improve the error translation logic within the FormikMarkdownField component.

CC: @bobbykolev @ccanos @SimoneZaza

[reactoholic]

When opening the PR for this ticket for some reason Travis is not building it successfully. Will investigate additionally why this is hapenning.