Faces Validation config parameters default value and deprecation

Talking with @BalusC on a previous issue he said to me that

https://github.com/eclipse-ee4j/mojarra/issues/5043#issuecomment-1048086850

> As to the params, the jakarta.faces.VALIDATE_EMPTY_FIELDS already defaults to true
and the other two have indeed an unfortunate default of false in name of strict backwards
compatibility. Although I'm personally not against flipping the defaults in a new major version ..
Feel free to open a new issue specifically on that.

**So I'm asking if it is not better to set**

`jakarta.faces.ALWAYS_PERFORM_VALIDATION_WHEN_REQUIRED_IS_TRUE = true`

and

`jakarta.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL = true`

**Probably these two parameters should be deprecated and removed as they bring more confusion than value**

https://balusc.omnifaces.org/2015/10/the-empty-string-madness.html

Start by reading the referenced discussion in jakartaee/faces#5043 and the linked article about empty-string handling. Review how the two named Faces validation parameters are currently defined and documented, then determine whether changing their defaults or deprecating/removing them is the intended scope. Done should include an agreed decision and project-specific acceptance criteria.

Written by the indexing model from the issue text.