Remove name attribute from internal pipelines API response

For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features

Deprecation Summary

The name attribute in the internal pipelines API is to be removed in 15.7.

Breaking Change

Not a breaking change for customers since this only affects the internal API. Our frontend has already been updated to start using the new event_type_name attribute (!101354 (merged)). It currently falls back to the name attribute if it cannot find the event_type_name attribute. This was done for multi-version compatibility (https://docs.gitlab.com/ee/development/multi_version_compatibility.html).

Affected Topology

The MR frontend uses the name attribute, in both Self-managed and SaaS. But users should not be affected by this deprecation since it affects only the internal API.

Affected Tier

Free

Checklists

Labels

This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
- A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page.
- Documentation has been updated to mark the feature as deprecated.
On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post.
On the major milestone:
- The deprecated item has been removed.
- If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.

Mentions

Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.
- To see who the stable counterparts are for a product team visit product categories
  - If there is no stable counterpart listed for Sales/CS please mention @timtams
  - If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
  - If there is no stable counterpart listed for Marketing please mention @cfoster3
Your GPM has been @mentioned so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.

Deprecation Milestone

15.6

Planned Removal Milestone

15.7