chore: support "formData" in swagger bindings parsing

[tayritenour]

Description

We are using the swagger generation in lore, and need to support openapi.json that describe endpoints with formData as well. This doesn't change anything about the current bindings (which I ran with make -C proto build && make -C bindings build && make -C master build && make -C proto gen-buf-image)

This is a workaround due to coupling with Lore. A proper fix ticket is here: https://hpe-aiatscale.atlassian.net/browse/MLG-1019

Test Plan

Commentary (optional)

Checklist

• Changes have been manually QA'd
• User-facing API changes need the "User-facing API Change" label.
• Release notes should be added as a separate file under docs/release-notes/.
  See Release Note for details.
• Licenses should be included for new code which was copied and/or modified from any external code.

Ticket

[netlify]

✅ Deploy Preview for determined-ui ready!

Name	Link
🔨 Latest commit	8ec6d50
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/651f175b18759a0008e2244a
😎 Deploy Preview	https://deploy-preview-8078--determined-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[szewaiyuen6]

What happen if we run this generation code on Lore, will there be no bindings created for the upload end point? Or the bindings would still be created but we just don't use it?

[tayritenour]

What happen if we run this generation code on Lore, will there be no bindings created for the upload end point? Or the bindings would still be created but we just don't use it?

When we run on Lore, it makes the bindings for all the objects and endpoints successfully. Before it was completely blocked from working so we need this allowance to do the build at all. The issue is that the generated endpoint for specifically anything that uses formData will not pass the files correctly. We need to do the supplemental work to actually support Multipart form data to use it. Ticket here: https://hpe-aiatscale.atlassian.net/browse/MLG-1019

In the mean time, caleb is okay with just calling the particular upload_files endpoint directly (rather than using the bindings). The reason being that doing this correctly looks complicated and would take me a while and I don't know if we can request the resources to do this quickly enough for the demo.

[szewaiyuen6]

Sounds good, thanks for the explanation.

[ashtonG]

looks fine!