(Resolve) Tech debt of the ConnectorForm

[timroes]

Brainstomring issue about problem with the ServiceForm component. Please feel free to list all issues that should be addressed to make this component more stable and easier to maintain:

• Refactor the ServiceForm to not contain connector type #13056
• Only render connector form component if the selected connector definition specification is loaded (move loading state and spinner into ConnectorCard) 🪟🔧 Move connector loading state into connector card #20127
• Remove component override for name field and make it a normal field in the schema with title and description 🪟🔧 Remove connector form name override #20132
• Move unfinished flows into local state in ConfirmationControls (reset from the outside if formik state becomes non-dirty) 🪟🔧 Remove top level state for unfinished flows in connector form #20135
• Remove uiWidgetsInfo state by finding the enum/const field defining the selected oneOf and adding it to the condition form block to check the selected value by looking at the formik state
• Only do default value calculation once before rendering the formik component the first time (remove PatchInitialValuesWithWidgetConfig hack)
• Build yup schema once by flattening the oneOf conditions into a single object and adding when conditions on the found condition key (remove RevalidateOnValidationSchemaChange hack)
• Add Consider default values for oneOf fields in connector specs #17352 to default value calculation

• Pull out auth field hiding from FormSection to a higher level when generating from the spec which fields should be rendered.
• values.connectionConfiguration plus flattened values are confusing (for a flattened form)
• Rethink default behavior (should it be sending the value if the field is empty?), since it's working different depending on your field type atm -> extra issue

[octavia-squidington-iii]

cc @airbytehq/frontend

[flash1293]

current selection for oneOf does not need additional state because the documentation states that each oneOf has a const property which is the same for each of the conditions (also checked via SAT): https://docs.airbyte.com/connector-development/connector-specification-reference/#using-oneof

Instead of storing this separately we can do the same thing the SAT is doing and search for the shared const field in each condition to determine the currently chosen path. This has the downside of breaking connectors which don't satisfy this SAT rule, but it seems justifiable in this case.

The derived formFields representation of the schema should include the detected "selected condition" keys for each condition node in the form, so the condition form node component itself as well as the yup schema building logic can look it up easily.

[flash1293]

Last of the stacked PRs is in review and received feedback already, should be merged soon

[flash1293]

Approved, waiting for the code freeze