Parse Maven build coordinates

[andrew]

Retain build plugins, plugin dependencies, plugin management entries, and build extensions when parsing project and profile build blocks.

This lets source-analysis callers inspect raw build coordinates without decoding a POM a second time and supports git-pkgs/manifests#48.

[Copilot]

Pull request overview

This pull request extends the POM parser to retain Maven build coordinates (plugins, pluginManagement, and extensions) from both project- and profile-level <build> blocks, enabling callers to inspect raw build-related coordinates without re-parsing the XML.

Changes:

• Add Build, PluginManagement, Plugin, and Extension types and expose Build on POM and Profile.
• Teach the streaming XML parser to decode <build> blocks, including plugin dependencies.
• Add a focused unit test validating project and profile build coordinate parsing.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
pom.go	Adds build-related data model types and exposes Build on POM and Profile.
parse.go	Extends the custom XML decoder to parse <build> blocks (plugins, pluginManagement, extensions).
pom_test.go	Adds coverage ensuring build coordinates are correctly parsed from both project and profile sections.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.