Run code quality in more pipelines

What does this MR do and why?

As explained in #378600 (closed), the code quality report is often broken because the artifact is missing in the latest pipeline on master. This occurs after merging QA MRs and Docs MRs. We should make sure to run code quality in those pipelines too so there is always an artifact to compare against in the latest pipeline on master.

We don't need to run in the MR pipelines for docs-only MRs, only after it merges to master.

• Resolves #378600 (closed)
• Related to #378718 (closed)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.