Allow Build Publish with `overwrite` Flag When Build Number is New

[bhanurp]

• [ ] All tests have passed. If this feature is not already covered by the tests, new tests have been added.
• [ ] The pull request is targeting the dev branch.
• [ ] The code has been validated to compile successfully by running go vet ./....
• [ ] The code has been formatted properly using go fmt ./....

---

Depends On

https://github.com/jfrog/jfrog-cli-artifactory/pull/55

Fix: Allow Build Publish with overwrite Flag When Build Number is New

Issue

When attempting to publish a build with the overwrite flag, the process fails if the buildName already exists in Artifactory but the buildNumber is new. The failure occurs due to a missing build number in Artifactory.

Current Behavior

• Publishing fails with an error stating that the build number is not available.

Solution

• Ensure that the build info is pushed even if the specified buildNumber is not yet available in Artifactory.

---

This PR adds functional tests to above case.