[Feature]: Allow ordering runbook input fileds

[NemausatTara]

Is your feature request related to a problem?

When creating a runbook, I'm defining all the input fields using this syntax:

inputA={{ .inputA
    | description "inputA description"
    | required
    | required "inputA is required"
    | squote
}}               

inputB={{ .inputB
    | description "inputB description"
    | type "select"
    | options "false" "true"
    | squote
}}  

When using my runbook on the Hoop web page, my input fields order does not respect the order I've used in the code (nor the alphabetical order).

Describe the solution you'd like

I would like the input field order to respect the code order, or I would like to be able to manage the input field order myself, with this kind of syntax:

inputA={{ .inputA
    | description "inputA description"
    | required
    | required "inputA is required"
    | squote
    | order 1
}}               

inputB={{ .inputB
    | description "inputB description"
    | type "select"
    | options "false" "true"
    | squote
    | order 1
}}  

Describe alternatives you've considered

No response

Priority

Medium - Would improve my workflow

Use Case

I'm creating runbooks with a lot of fields. Some fields are optional and should appear after the mandatory ones.
Some fields correspond to the same concept and should be grouped together (ex of input fields: client_id & client_secret).

Mockups or Examples

No response

Additional Context

No response

Contribution

• I would be willing to submit a PR to implement this feature

Code of Conduct

• I agree to follow this project's Code of Conduct

[NemausatTara]

Hello Hoop community 👋

I was unable to find a way to order my runbooks input fields and could not find any related doc.

I'm sure this feature (if it does not exist yet) would enrich both the developers & users experience.

Have a nice day!

[pp0rtal]

Thank you @rogefm for #1261 🙏
We will upgrade to https://github.com/hoophq/hoop/releases/tag/1.49.5