fix: Value Stream Analytics Label Logic

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

While trying to implement this resource in a project, I noticed that the label logic error was being thrown when it shouldn't have been. Revisted logic and updated. Verified logic works as expected with added tests. Found a misspelling in one of the event names.

added Leading Organization label

Thanks for your contribution to GitLab @calee1! 🎉

• If you need help, page a coach by clicking here or come say hi on Discord.
• When you're ready, request a review by clicking here.
• We welcome AI-generated contributions and offer complimentary access to GitLab Duo!
• To add labels to your merge request, comment @gitlab-bot label ~"label1" ~"label2".

This message was generated automatically. Improve it or delete it.

added Community contribution workflowin dev labels

assigned to @calee1

changed the description

This merge request will be counted as part of the running Hackathon!

Find yourself in the Hackathon Leaderboard or check out the Hackathon page for more information! 🎉

This message was generated automatically. Improve it or delete it.

added Hackathon label

This merge request will be counted as part of the running Hackathon!

Find yourself in the Hackathon Leaderboard or check out the Hackathon page for more information! 🎉

This message was generated automatically. Improve it or delete it.

	1 Warning
⚠️	This merge request does not refer to an existing milestone.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Reviewer	Maintainer
@timofurrer (UTC+1)	@patrickrice (UTC+0)

If needed, you can retry the 🔁 danger-review job that generated this comment.

Generated by 🚫 Danger

changed the description

added 1 commit

• 5c6cbd2b - Removed unnecessary preconfigs

Compare with previous version

@gitlab-bot ready @PatrickRice

added workflowready for review label and removed workflowin dev label

requested review from @PatrickRice

Hi @timofurrer! Please review this documentation merge request. This message was generated automatically. Improve it or delete it.

added documentation twtriaged labels

requested review from @timofurrer

@PatrickRice @timofurrer, this Community contribution is ready for review.

• Do you have capacity and domain expertise to review this? If not, find one or more reviewers and assign to them.
• If you've reviewed it, add the workflowin dev label if these changes need more work before the next review.
• Please ensure the group's Product Manager has validated the linked issue.

This message was generated automatically. Improve it or delete it.

	1 Warning
⚠️	This merge request does not refer to an existing milestone.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Reviewer	Maintainer
@timofurrer (UTC+1)	@patrickrice (UTC+0)

If needed, you can retry the 🔁 danger-review job that generated this comment.

Generated by 🚫 Danger