Speed up Gitlab CI by using fewer steps in the pipeline

When I was writing on how to do Flutter test reports in Gitlab Ci I noticed my pipeline was split into three steps:

• linting
• test run
• coverage report

When I first set this up, it felt “prettier” to me. They were all independent and if one step failed I could easily see which.