wet-boew wb-frmvld form validation on specified fields

Problem/Motivation

This form validation mode is now included in WxT 6.1.3+

Each webform now gets an optional WET-BOEW Form validation mode, enable it with a checkbox in each webform (settings).
Also need to ensure that clientside validation in the webform it'self is not disabled (again, webform settings).

To ensure it works you'll also need to uninstall the clientside_validation / webform_clientside_validation module(s) (If installed).

Original issue statement:

When a form is wrapped in

<div class="custom-wrapper wb-frmvld">'
</div>

This wrapped div when around a form that uses the wet-boew library, enables wet-boew form validation. This wet-boew form validation adds some interesting accessibility however it breaks features like webform conditionals provided by the Webform module designed for Drupal 9 or Drupal 10.

Additional context

• https://drupal.org/project/webform
• https://wet-boew.github.io/v4.0-ci/demos/formvalid/formvalid-en.html
• https://drupal.org/project/wxt
• https://github.com/wet-boew/wet-boew/issues/9498

Steps to reproduce

1. Create a new web form with the state-of-the-art wxt distribution.
2. Put a prefix: '#prefix': '<div class="custom-wrapper wb-frmvld">'
3. Put a suffix: '#suffix': '</div>'
4. Adds conditions for a field, say a field's visibility depends on another field's options.
5. Visit the web interface of the created form
6. No conditions will work
7. Remove suffix/prefix
8. Test again, all conditions will work as designed.

Proposed resolution

the build and compile instructions for wet-boew are here:

https://wet-boew.github.io/v4.0-ci/docs/start-en.html

I haven't tested these build/compile instructions yet but it's a good starting point.
See upstream issue:
https://github.com/wet-boew/wet-boew/issues/9498

Remaining tasks

Set up a wet-boew development build,
the build and compile instructions for wet-boew are here:

https://wet-boew.github.io/v4.0-ci/docs/start-en.html

Debug the functionality related to wb-frmvld (wet-boew form validation), pay attention particularly to any javascript that removes events, add event bindings/namespaces use namespaces for wet-boew that don't conflict with others, change the logic to remove the namespaced wet-boew events and regenerate the events using wet-boew namespaced events, do not remove existing events, examine if the DOM changes are breaking webform conditionals, debug and fix the problem

User interface changes

N/A

API changes

TBD