Transfer config - Precheck for Docker repo names

[yahavi]

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

---

Add precheck runner for repository naming.
Usage: jf rt transfer-config <source> <target> --prechecks

The runner verifies that Docker repositories does not contain the characters . or _ and generates a CSV file with the illegal repository names, if any.

Example
Log:

2023/11/05 10:10:41 [Info] == Running check (1) 'Repositories naming' ======
2023/11/05 10:10:41 [Info] Found 2 illegal repository names. Check the summary CSV file in: /Users/yahavi/.jfrog/logs/illegal-repository-names-2023-11-05.10-10-41.csv
2023/11/05 10:10:41 [Info] Check 'Repositories naming' is done with status Fail
2023/11/05 10:10:41 [Info] == Running check (2) 'Remote repositories URL connectivity' ======
2023/11/05 10:10:41 [Info] Check 'Remote repositories URL connectivity' is done with status Success

CSV file:

RepoKey,Reason
asdas_sadas,Docker repository keys in the SasS are not allowed to include '.' or '_' characters.
asdasd.a,Docker repository keys in the SasS are not allowed to include '.' or '_' characters.

[github-actions]

---

🐸 JFrog Frogbot

[eyalbe4]

Let's also create a PR to add "underscore" to the following limitation in https://docs.jfrog-applications.jfrog.io/jfrog-applications/jfrog-cli/cli-for-jfrog-cloud-transfer

7. Docker repositories with names that include dots aren't allowed in JFrog Cloud.

In the same documenytation link about, let's also fix the link in -

4. Run the file transfer pre-checks as described [here](https://github.com/jfrog/jfrog-cli-core/pull/1018/files).