TextInput/TextinputGroup - consistent status/validation prop naming

Describe the enhancement or change
Related to convo chain at https://github.com/patternfly/patternfly-react/pull/10815#discussion_r1697713753

Would also pertain to other components that have a status/validation type prop. We should align on:

• whether the prop should be status or validation (personally would lean towards status)

• whether the prop type should only include valid class values, e.g. success, error/danger (another thing to align on), warning, info, and custom, or whether there should also be a "default" value to sort of unset it. If the latter, then does "default" make sense or should it be "none" or something else?

Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?

Any other information?

Jira Issue: PF-32

Commencez par la discussion de la pull request liée et les définitions des props de TextInput et TextinputGroup. Examinez les autres composants dotés de props d’état ou de validation, puis tranchez les questions de nommage et de valeurs autorisées ; la tâche est terminée lorsque les conventions sont convenues et appliquées de manière cohérente.