Change behaviour of --config-file flag with config commands

[silvanocerza]

Please check if the PR fulfills these requirements

• The PR has no duplicates (please search among the Pull Requests
  before creating one)
• The PR follows
  our contributing guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

• What kind of change does this PR introduce?

Changes the behaviour of config init and config dump when using the --config-file flag.

• What is the current behavior?

config init --dest-file <some_path_file> doesn't initialize a new config file using the specified path and always overrides existing file in default config path.

Calling config init --dest-file <path> --dest-dir <path> creates a new config file in path specified by --dest-dir.

Calling config dump --config-file <some_path_file> always prints the default configurations.

• What is the new behavior?

Calling config init --dest-file <some_path_file> initializes a new config file using the specified path, if the file exists and the --overwrite flag is not set an error is returned, otherwise a new file is created.

Calling config init --dest-file <path> --dest-dir <path> now returns an error.

Calling config dump --config-file <some_path_file> prints the configuration file specified.

Calling config dump --config-file <some_path_file> --additional-urls=<urls> prints the configuration file specified but additional_urls are overridden by the ones specified with the flag.

• Does this PR introduce a breaking change?

I don't think so. 🤔

• Other information:

None.

---

See how to contribute

[ubidefeo]

tested and approved