Clarify expectations for roles involved in managing Zowe clients' team configs

[adam-wolfe]

Is your request for enhancement related to a problem? Please describe.

We should try to avoid giving individual users the impression that they will need to become team config experts to be successful with Zowe CLI/Explorer for VS Code.

Describe the solution you'd like

We should be positioning team config as something that is managed by a single person (who understands team config and has access to the networking/environment information necessary to access services running on the mainframe) and shared with a team. The shareability of team config is one of its primary benefits. Some of this is spelled out in other pages in the documentation, but this is not so clear in the pages listed below.

Related doc pages

https://docs.zowe.org/stable/user-guide/cli-using-initializing-user-configuration
https://docs.zowe.org/stable/user-guide/cli-using-editing-team-configuration

Additional context