Investigate using a standard form validation library

[nwmac]

Look at the 2 main Vue form validation libraries and see if using one of these would help.

Figure out how to wire in our existing validators to it, if so.

[torchiaf]

Candidates:

• Vuelidate
• VeeValidate

[rak-phillip]

Related Rancher Desktop discussion - rancher-sandbox/rancher-desktop#3376

[cnotv]

While evaluating alternatives to our form validation, we have to consider existing logic and edge cases which range from trivial to boring to very convoluted.

Out of my mind I can list these:

• Integration of the validation to the tabs
• Binding to the CruResource component for the
  • Validation (fvFormIsValid)
  • Error messages merge (fvUnreportedValidationErrors)
  • Action button status mapping
• Mapping of the rules from a configuration file to the editor, with tests
• Integration to the existing components with fvGetAndReportPathRules
• Integration to components passing a dictionary of rules fvGetAndReportPathRules
• Keep existing rules and tests

It would be also convenient to have the ability to validate component separately and map them to the form, so we may have the possibility to add validation directly to them and avoid repetition to each view, e.g. the case with the key duplication

[cnotv]

Other cases which may have been missed were mentioned in the documentation update issue https://github.com/rancher/dashboard/issues/7150

[cnotv]

Considerations about validation logic, which may eventually close this https://github.com/rancher/dashboard/issues/6159

[nwmac]

@gaktive Changing milestone to 2.10.0