Print fatal matches first under GitHub Actions

[KamilaBorowska]

Currently when running GitHub Actions there is no particular ordering to displaying GitHub Action specific output, as can be seen here.

ansible-lint/src/ansiblelint/app.py

Lines 96 to 100 in e248b64

	# If run under GitHub Actions we also want to emit output recognized by it.
	if os.getenv("GITHUB_ACTIONS") == "true" and os.getenv("GITHUB_WORKFLOW"):
	formatter = formatters.AnnotationsFormatter(self.options.cwd, True)
	for match in matches:
	console.print(formatter.format(match), markup=False, highlight=False)

I think fatal matches should be printed first due to GitHub Actions' limit of 10 warnings and 10 errors (https://github.com/orgs/community/discussions/26680) - generally displaying things that actually impact the build is more useful than showing already known issues, considering anything beyond that cap won't be displayed by GitHub.

Doing this would make progressive mode more useful when using GitHub Actions.