Fix: Empty Build Info When Using Maven Plugin Goals

[agrasth]

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• All static analysis checks passed.
• Appropriate label is added to auto generate release notes.
• I used gofmt for formatting the code before submitting the pull request.
• PR description is clear and concise, and it includes the proposed solution/fix.

---

Fix: Empty Build Info When Using Maven Plugin Goals (deploy:deploy-file)

Error: Build promotion succeeds but artifacts aren't actually promoted. Setting properties fails with 404 (artifacts not found in repository).

Root Cause

The isDeploymentRequested() function only checks for exact string matches of "install" or "deploy", but Maven plugin goals use the format plugin:goal (e.g., "deploy:deploy-file").

This causes:

1. deploy:deploy-file not recognized as deployment goal
2. publish.add.deployable.artifacts = "false" is set
3. Build Info Extractor skips artifact collection
4. Build info published with only dependencies, no artifacts

Log Evidence:

[main] INFO org.jfrog.build.extractor.maven.BuildInfoRecorder - Artifact metadata not requested - skipping artifact collection for build info

[fluxxBot]

we can use an array to store this, and you can search using strings.contain

[agrasth]

Contains() creates false positives by matching substrings anywhere in the goal name (e.g., "uninstall" contains "install", "reinstall" contains "install")
If we use this we might have to handle more cases separately, WDYT?

[fluxxBot]

I meant something like arr := [":deploy", "deploy", "deploy:"]
and arr.Contains(":deploy")

arr can be reusable down the line
looks good?

[fluxxBot]

what about ":deploy" and ":install", there inconsistency w.r.t above file

[agrasth]

Done

[fluxxBot]

you can also us the above discussed array here