Remove requirement report `pipeline` attribute from GraphQL
What does this MR do?
Since we use build instead of pipeline for requirement test reports, we need to de-expose pipeline from GraphQL (and within %13.1).
It looks like builds aren't exposed via GraphQL so we'd have to do that in a later MR. This one just removes pipeline so we don't have to deprecate it later once it's released (smallest unit of work).
Related to #215518 (closed) and #219999 (closed)
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Justin Farris