Improve the ordering of GHA workflow fields

[deimantastumas]

Summary

When building the YAML file (GHA workflow) using the workflow structs defined in ./octo/actions/**, IF conditional is placed above the step name. This behaviour is not optimal as it's much easier to read workflows where conditionals are used below the step name. This can be easily fixed by switching the fields in the defined structs.

Examples of workflows used in acknowledged repositories where conditional is placed below the name, proving the common practice:

• https://github.com/tldr-pages/tldr/blob/main/.github/workflows/ci.yml#L39
• https://github.com/appsmithorg/appsmith/blob/release/.github/workflows/server.yml#L100

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).

[dmikusa]

Thanks for the PR. I'm not opposed to making this change, but I need to do some testing and see how this impacts our pipelines. I assume that it shouldn't change any functionality, just the readability of the YAML.

In the meantime, I would also suggest that you add comments above the struct explaining the struct (maybe how it maps to the GHA YAML) and making a note that order is intentional for the reason you shared. Just a sentence or two should be plenty. Otherwise, I could see someone accidentally changing this in the future, or possibly a formatter reshuffling them.

[deimantastumas]

Addressed your review. Thank you!