Reformatted config files to not fail common linters (closes #2890)

[andrewvaughan]

Fixes #2890

Important - I am still unable to run tests locally, so a solid code-review would be very-much appreciated.

Additionally, I believe that the change of the job name from build to megalinter - while extremely important for people who build automation scripts that reference the build name (like myself) and need something more specific than "build", this may end up being a breaking change if anyone has built such scripts or dependencies in the past. Please keep this in mind for release policies.

Proposed Changes

1. Used more-advanced YAML to better-format config files so they don't fail with common linters (especially those that enforce line-length)
2. Changed the workflow job name from a generic build which can conflict with other workflows to megalinter

Readiness Checklist

Author/Contributor

• Add entry to the CHANGELOG listing the change and linking to the corresponding issue (if appropriate)
• If documentation is needed for this change, has that been included in this pull request

Reviewing Maintainer

• Label as breaking if this is a large fundamental change
• Label as either automation, bug, documentation, enhancement, infrastructure, or performance

[nvuillam]

Looks good to me, thanks a lot for your contribution :)

[nvuillam]

@andrewvaughan it would reassure me if you can test a little with npx mega-linter-runner@beta --install before we release a new version :) ( otherwise I'll test it myself but I have some time availability issues these days ^^ )