Support for Distribution path mapping with AQL

[YardenEdery]

• 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 ./....

---

Added support of "pathMapping" property to file spec in order to have the ability to control where to distribute the artifacts that are being added dynamically when using AQL in the release bundle that is being created.

When looking for docker artifacts using AQL, the release bundle also includes, in the distribution server backend, all the layers for a manifest.json and all of the manifest.json files and their layers if its a list.manifest.json

From now on the "pathMapping" will take affect on those none specified added manifests and layers and will allow the users a native way of creating the file spec for distribution commands.

FYI This couldn't be achieved using "target" for the list.manifest.json example.

[github-actions]

---

🐸 JFrog Frogbot

[eyalbe4]

• Let's add a complete description to this PR, explaiining the new functionality,
• Let's create a documentation PR to https://github.com/jfrog/documentation. This documentation repository include the source content for JFrog CLI's online documentation available at https://docs.jfrog-applications.jfrog.io/jfrog-applications/jfrog-cli.
  I suggest adding a few examples to https://docs.jfrog-applications.jfrog.io/jfrog-applications/jfrog-cli/cli-for-jfrog-distribution and also updating https://docs.jfrog-applications.jfrog.io/jfrog-applications/jfrog-cli/cli-for-jfrog-artifactory#using-file-specs

[eyalbe4]

Unnecessary change which adds a redundant new-line.

[YardenEdery]

But gofmt makes the go file end with a newline, are you sure not to align this on current file?

[YardenEdery]

Should we also create documentation in:
https://jfrog.com/help/r/jfrog-cli/cli-for-jfrog-artifactory

[yahavi]

Suggested change

	"description": "If specified, determines release-bundle source and target paths for artifacts that had been fetched using aql",
	"description": "If specified, determines release-bundle source and target paths for artifacts that had been fetched using aql.",

[yahavi]

Configuring pathMapping is challenging and the documentation does not explain how to do it. Let's add an example:

Suggested change

	"description": "The input path for mapping."
	"description": "The input path for mapping.",
	"examples": ["(.*)/old_folder/(.*)"]

[yahavi]

Suggested change

	"description": "The output path for mapping."
	"description": "The output path for mapping.",
	"examples": ["$1/new_folder/$2"]

[yahavi]

Please also update go.mod and go.sum with the tip of dev branch to reflect the changes in jfrog/jfrog-cli-core#1031

[yahavi]

Could you please also add a description to this PR?