Feature/1275 add metadata option to deploy

[JoernBerkefeld]

PR details

What changes did you make? (Give an overview)

• closes [FEATURE] add --metadata option to deploy #1275

Further details (optional)

...

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• test scripts updated
• Wiki updated (if applicable)

[github-actions]

Coverage Report

Commit:dfd81bf
Base: develop@66a2008

Type	Base	This PR
Total Statements Coverage	65.49%	65.79%  (+0.3%)
Total Branches Coverage	66.27%	66.85%  (+0.58%)
Total Functions Coverage	75.37%	75.45%  (+0.08%)
Total Lines Coverage	65.49%	65.79%  (+0.3%)

Details (changed files):

File	Statements	Branches	Functions	Lines
lib/Deployer.js	80.67%	70.42%	100%	80.67%
lib/Retriever.js	82.72%	75%	100%	82.72%
lib/cli.js	0%	0%	0%	0%
lib/index.js	69.02%	56.08%	67.64%	69.02%
lib/metadataTypes/SenderProfile.js	87.71%	70%	100%	87.71%
lib/util/util.js	80.85%	79.71%	85.29%	80.85%

[JoernBerkefeld]

https://github.com/Accenture/sfmc-devtools/wiki/06.b-~-Standard-Commands/_edit

deploy

Command: mcdev deploy [business unit] [metadata type] [metadata key] [--metadata] [--fromRetrieve] [--refresh] [--changeKeyValue=yourNewKey] [--changeKeyField=otherFieldInJson] [--execute] [--schedule] [--fixShared]

Alias: mcdev d

[...]

deploy specific type and key via --metadata option:

This option is exceptionally flexible because it allows you to specify multiple type-key combos simultaneously. If set, it overrides the type or key you specified the old-fashioned way.
If the respective type features it, you can combine keys, IDs, and names in your selection. If you specify multiple --metadata parameters (or -m as an abbreviated version), the keys/ids/names are looked for separately, similar to an OR-search in SQL.