Fix root module name handling in build info collection

[EyalDelarea]

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• All static analysis checks passed.
• This pull request is on the dev branch.
• I used gofmt for formatting the code before submitting the pull request.

---

Bug Description:

When collecting build information for different packages, if the module name is not specified in the descriptor file or provided as a CLI argument, it defaults to an empty string. This results in an error from the Artifactory server, stating that the module ID cannot be null.

16:22:54 [Error] server response: 400 
{
  "errors": [
    {
      "status": 400,
      "message": "Module id name cannot be null!"
    }
  ]
}

In previous CLI versions, the default value was ":", which prevented crashes.

Fix:

If no module ID is provided, the default will now be set to the base directory of the module. This aligns with the default behavior of package descriptors init scripts.
As a last reasort the module name will resolve to "module" to be displayed at the UI and not fail on publish.

[EyalDelarea]

@yahavi i've changed the function to return error if fails to get working dir.
let me know what you think 🚀

[github-actions]

---

🐸 JFrog Frogbot

[kunkka-m]

I used the latest version of jfrog-cli(2.63.0), but this issue still happened

[kunkka-m]

Oh, This MR is to dev branch!

[lincoohe]

Hi @EyalDelarea ,it should be the build-publish issue instead of bce issue.