Follow-up from "Replaces yamlErrorMessags with errorMessages in headerbadges"

The following discussion from !179045 (merged) should be addressed:

• @lauraXD started a discussion: (+2 comments)

  @bsandlin we could keep yamlErrorMessages() if we return this.pipeline?.yamlErrorMessages , couldn't we? or should we keep it to one single error for now?

assigned to @lauraXD

mentioned in merge request !179045 (merged)

@sunjungp This is for the tooltip in the yaml invalid badge in the pipeline header. Do you want all available yaml errors to be displayed in the tooltip? Currently we just have the first one.

@bsandlin Yes, I think that would be more consistent, thanks for creating the follow-up here! I'll add some relevant labels so we don't lose track.

I was considering adding this to our usability enhancement epic &16354 but not sure. Please feel free to assign it to another epic if you find a more suitable!

@sunjungp I think that's a good place for it

added grouppipeline authoring label

added devopsverify sectionci labels

added backend label

added usability label

changed milestone to %Backlog

@lauraXD changing this one to frontend and un-assigning you

Thank you!

removed backend label

added frontend label

unassigned @lauraXD

added gitlab-org#16354 as parent epic

added maintenanceusability typemaintenance labels

mentioned in issue gitlab-org/quality/triage-reports#22302 (closed)

mentioned in issue gitlab-org/quality/triage-reports#22380 (closed)

mentioned in issue gitlab-org/quality/triage-reports#22486 (closed)

mentioned in issue gitlab-org/quality/triage-reports#22681