Remove formik Field components from UI layer

[zephraph]

When we first started integrating Formik into the console we really didn't have much of a separation between the UI of a form element and its actual logical behavior. Given that, we added the Field component in our form UI components. This has a few downsides:

1. It necessitates that the UI layer includes formik as a dependency if we ever ship it separately
2. It requires that any UI form component only be rendered inside the context of a formik form

This tight coupling has already caused a few minor issues. I'm working on richer table selection behavior to address #1060 and I ran into it but it's not the first time I've ran across it.

Also, we've got #804 where we're actively considering migrating away from Formik. This would be the first required step either way.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
console-ui-storybook	✅ Ready (Inspect)	Visit Preview	Jul 21, 2022 at 5:45PM (UTC)

[zephraph]

Made this configurable so we could pass down number, etc

[david-crespo]

Awesome! I did a search for formik in libs/ui and found the FormikDecorator, which we were using to make Storybook stories not break due to missing Formik context. I think that can go too, taking this even further negative LoC. Love it!