guide: extract part of theconfig cmd ref.

[jorgeorpinel]

The Configuration sections is too long for the cmd ref. Probably the best route is to extract the parts of the current cmd ref description and all the config options into a new User Guide, and leave the rest in the cmd ref.

From #331 (review)

---

UPDATE from #1368 (comment):

It's not a well known or documented feature of DVC, but DVC merges sections with same name from different configs

^ This can be part of the intro or index to the configuration guide.

• Include basic remote storage config info and/or link to https://dvc.org/doc/user-guide/data-management/remote-storage

[jorgeorpinel]

I've updated the issue description to include:

Probably the best route is to extract the parts of the current cmd ref description and all the options into a new User Guide, and leave the rest in the cmd ref.

What do you guys think? Sorry it took so long!

[shcheklein]

@jorgeorpinel yep, agreed. I would start probably by writing User Guide and taking some parts from the commands reference. When it's ready we'll clean the CR sections and put the appropriate links.

[jorgeorpinel]

Another important aspect to include, from #1368 (comment) 👍🏼

if we define a remote (name and all settings) in a local config (for security concerns) all other team members have to agree on the url and potentially name for the remote as well.
It's not a well known or documented feature of DVC, but DVC merges sections with same name from different configs...
in the regular .dvc/config
in the local config - .dvc/config.local
...
same idea, but you should be using --system or --global configs
the config behavior could use some documentation

Also relates to #2866

[dberenbaum]

Lowering priority due to lack of resources