Passing optional client-side validation props into the formik config

[monotasker]

Description

Allows custom deposit forms the option of using formik's client-side validation, while changing nothing about the form's server-side validation.

Formik's client-side validation capabilities are currently not accessible to anyone who is building a custom deposit form (i.e., overriding the RDMDepositForm component). There is no way to pass the client-side validation props from RDMDepositForm through to formik. This commit makes client-side validation accessible by passing two props ("validate" and "validationSchema") into formik config via DepositFormApp and DepositBoostrap. This way developers can choose either to pass through a validation function or to pass through a yup schema which formik understands.

These two props default to undefined in which case they are ignored. They do not interfere at all with the current server-side validation. So there's no risk or negative side-effect to passing them through.

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• I'm aware of the code of conduct.
• I've created logical separate commits and followed the commit message format.
• I've added relevant test cases.
• I've added relevant documentation.
• I've marked translation strings (for relevant code).
• I've followed the CSS/JS and React guidelines (for relevant code).
• I've followed the web accessibility guidelines (for relevant code).
• I've followed the user interface guidelines (for relevant code).
• I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• I've NOT included third-party code (copy/pasted source code or new dependencies).

Third-party code

If you've added third-party code (copy/pasted or new dependencies), please reach out to an architect.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.

[github-actions]

This PR was automatically marked as stale.