(refactor) FormField attribute 'Type' should be Optional

[Twiineenock]

Requirements

• This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes a conventional commit label. See existing PR titles for inspiration.
• My work conforms to the OpenMRS 3.0 Styleguide and design documentation.
• My work includes tests or is validated by existing tests.

Summary

Markdown questions have no question type hence should be optional in the form schema.
This related to the work coming in from here We should make this optional since markdown content doesn't have a type

Screenshots

Related Issue

Other

[NethmiRodrigo]

LGTM! @samuelmale we had to make type optional as well. Does that seem okay?

[samuelmale]

This makes sense and I'm not opposed to the idea.

Markdown questions have no question type hence should be optional in the form schema

The FE defines a pseudo type called control (see) and I believe it should be used in such scenarios. If this makes sense, we can have this type as a reasonable default in the form-builder. cc: @denniskigen

           {
             "type": "control"
              "value": [
                "**This form is used to**:showcase feature of the react form engine",
                "### This is just an **explainer text** example  in *markdown*"
              ],
              "questionOptions": {
                "rendering": "markdown"
              },
              "id": "heading2"
            }

[denniskigen]

Seems reasonable to me, @samuelmale!

[NethmiRodrigo]

@samuelmale that makes sense! Shall we opt to do that instead then, default type to the value control, without making it optional? FYI @Twiineenock

[samuelmale]

Shall we opt to do that instead then, default type to the value control, without making it optional?

Makes sense to me!

[NethmiRodrigo]

Closing this PR in favor of making the type to control for markdown content