[2/2]: ENG-2806 Ensure Integration Form Validation Works

[agiron123]

Describe your changes and why you are making these changes

This PR ensures that integrations form validation works properly after changing form input empty state from null to empty string (this was needed to fix a console error message).

Depends on: #1218

Related issue number (if any)

ENG-2806

Loom demo (if any)

https://www.loom.com/share/eb58d20deee64922b83841fcb6bf7362

Checklist before requesting a review

• I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
• I have performed a self-review of my code.
• I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
• If this is a new feature, I have added unit tests and integration tests.
• I have run the integration tests locally and they are passing.
• I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
• All features on the UI continue to work correctly.
• Added one of the following CI labels:
  • run_integration_test: Runs integration tests
  • skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

[agiron123]

TODO: @agiron123 address comments from slack here.

[likawind]

Great, will these be covered by react class and react hook form later?

[agiron123]

Great, will these be covered by react class and react hook form later?

@likawind Yes, validations here will go through react-hook form later. However, I do expect them to remain mostly the same. Maybe a small amount of syntactic sugar that react-hook-form provides, but not too many changes in terms of how we validate.