Refactor pipeline form parsing

[Ziyang-98]

Changelogs:

Backend

• Updated BE Pipeline FormField with the following fields
  • Title as the display title for the form field
  • Description as the display description for the form field
  • Required to determine whether field is mandatory (Note that checkboxes field don't have this)
  • MinLength for input field minimum length
  • Options for select and checkboxes fields
  • Default as the default option for select field
• Implemented more validations for FormField
• Added validation FormField in handleCreatePipeline which returns error if validation fails

Frontend

• Refactored types for JsonFormComponent to mirror BE FormField model and updated all related objects to follow types
• Updated rjsf parsing methods to convertform object into rjsf formSchema and uiSchema
• Implemented more validations for form when creating a pipleine

Bruno

• Added the fetch all pipeline API

Notes

• Right now the BE returns a generic Bad Request error message for handleCreatePipeline. Would be better if the BE can return the validation message directly, but I'm not sure how to return custom error messages in Go. @joshtyf need your advice and opinion on this.
• Currently the FE has more validations than BE. (for e.g., FE checks for whether form field names are unique while BE doesn't) I didn't implement those validations in the BE for now as I thought that the current ones are sufficient for an MVP, but in the future the validations in BE can be supplemented to match the FE.

Demo

Demo for the flow of creating a Pipeline with Form to displaying of the Form in Service Request page. Showcased some of the validation too.

2024-04-13.17-15-43.mp4

Closes #92

[joshtyf]

Changes are fine, but not really sure the intent behind it.

[joshtyf]

Right now the BE returns a generic Bad Request error message for handleCreatePipeline. Would be better if the BE can return the validation message directly, but I'm not sure how to return custom error messages in Go. @joshtyf need your advice and opinion on this.

Let's do this in a separate PR as this is quite big already. It's a good suggestion. Let me create the change

[joshtyf]

LGTM