Migrate the OIDC auth provider form to use vee-validate

[rak-phillip]

Summary

This migrates the custom validation implementation for the OIDC auth provider to a pure vee-validate/zod implementation.

Fixes #17754

Occurred changes and/or fixed issues

• Migrate computed props to composition api for oidc
• Validate oidc auth provider form with vee-validate/zod
• Add vee-validate to ArrayList
• Fix unit tests

Technical notes summary

In order to get this to work with useForm from vee-validate, we need to find a way to sync values from the form's mixins with the composition API. This is currently accomplished via watchers that exist to sync values with the refs (99078ad). I think that the proper, long-term solution will be to migrate away from mixins to the composition API. Take care in reviewing this pattern, there's a higher risk of errors with the current approach.

The validation approach using vee-validate/zod is used to demonstrate validation without the form-validation mixin or bridge in use. More information about the patterns represented in this PR can be found in the vee-validation documentation: https://vee-validate.logaretm.com/v4/guide/composition-api/typed-schema/#zod

Areas or cases that should be tested

Test configuring the Keycloak auth provider. Instructions for getting started can be found in: https://github.com/rancher/ui-internal-tools/tree/main/keycloak

Areas which could experience regressions

There are risks that the authentication logic has been unintentionally altered with this change. Edge-cases could need additional consideration. For example, what happens if the form passes validation in the UI, but the server rejects the form?

Screenshot/Video

Inline validation errors

URL validation

ArrayList validation

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

[codyrancher]

Good with me on the technical side.

I think you still wanted to get the opinion of UX, if not I think I'd want to talk about the array list error indicator.

[rak-phillip]

I think you still wanted to get the opinion of UX, if not I think I'd want to talk about the array list error indicator.

Yes, I am scheduling time to discuss this with @oboc-sts next week, as well as a few other design changes that have come through with recent PRs.