fix(NA): yarn_lock_v1.ts parser for aliased packages

[mistic]

When yarn v1 merges aliased packages (like d3-color aliased to @elastic/kibana-d3-color) into a single yarn.lock header, the parser assumed all entries shared the same package name. It extracted the name from the first entry (@elastic/kibana-d3-color) and stripped it from all entries to compute versions, producing garbage for entries with a different name (d3-color@1 - 2).

So in this PR:

• Each header entry is now parsed individually to extract its own name and version
• Entries are grouped by package name using a Map<string, string[]>
• The block body (version, resolved URL, integrity, dependencies) is parsed once
• A separate PackageInfo is created for each unique name, so both d3-color@2.0.1 and @elastic/kibana-d3-color@2.0.1 are properly indexed

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[macroscopeapp]

Approvability

Verdict: Needs human review

This is a bug fix to dev tooling (yarn.lock parser) with tests, but the author does not own these files—they belong to @elastic/kibana-operations. The designated code owners should review changes to their infrastructure tooling.

^{You can customize Macroscope's approvability policy. Learn more.}

[tylersmalley]

@mistic did you see #259640? Does this do anything different?

[mistic]

I've only got in touch with the other PR after I put mine up. The end results are similar but I just think this changes are a closer fit to the past code structure that we had there before. Up to decide if we either close this or still merge it . I'm okay either way

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: ab885a3

Metrics [docs]

✅ unchanged

History

• 💚 Build #416776 succeeded 8524054

cc @mistic