Dividing mvd-configuration.md file into smaller topics

[ArooshLele]

List the file(s) included in this PR:
mvd-configuration.md

Describe your pull request here:
The mvd-configuration.md file has the Advanced Application Framework Configuration topic.
It is a large topic.
Following my discussion with Sean @1000TurquoisePogs , this large topic could be divided into smaller chunks/subtopics. The content stays the same.

The subtopic files would be as follows:

• accessing-zss.md
• configuration-file.md
• configuring-the-framework-as-a-mediation-layer-client.md
• setting-up-terminal-app-plugins.md
• network-configuration.md
• configuration-directories.md
• app-plugin-configuration.md
• logging-configuration.md
• zss-configuration-1.md
• using-multiple-zis-instances.md
• controlling-access-to-apps.md
• controlling-access-to-dataservices.md
• customizing-security-plugins.md
• administering-the-servers-and-plugins-using-an-api.md
• managing-cluster-mode-for-app-server.md

After creating the PR, follow the instructions in the comments.
@gauravs-20 @ArooshLele

[github-actions]

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

• Add the label review: doc.
• Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
• Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
  • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
• Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
• Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

[github-actions]

🚀 Deployed on https://6937b52cd054d22736980a20--zowe-docs-master.netlify.app

[Martin-Zeithaml]

2x: Medation -> Mediation

[Martin-Zeithaml]

I would suggest to provide full examples with yaml syntax:

```yaml
components:
  app-server:
    logLevels:
      _zsf.routing: 0
      _zsf.install: 0
```

```yaml
components:
  zss:
    logLevels:
      _zss.traceLevel: 0
      _zss.fileTrace: 1
```

[ArooshLele]

@Martin-Zeithaml Thanks, Martin for providing feedback. I've incorporated your feedback.
CC: @gauravs-20 @ArooshLele

[Martin-Zeithaml]

Missing top level curly braces, same with the second example:

{
  "host": <hostname>
  "port": <port>
  "security": {
    type: <"telnet" or "tls">
  }
}

[ArooshLele]

@Martin-Zeithaml Thanks. Based on your feedback, the file has been updated. CC: @gauravs-20

[1000TurquoisePogs]

I will not comment on the content of the pages because it's unchanged. We can improve pages in later PRs.

My feedback is on organization.
When splitting our 1 advanced config page into many, I think we need some categorization to guide users to the topics they are interested in.

It's always hard to determine where content should go: user-guide/installing, using, extending...
For now we can keep everything in user-guide/installing. But let's categorize these topics somehow.

[1000TurquoisePogs]

how about categorizing these pages somehow

app-server:

• "user-guide/managing-cluster-mode-for-app-server",

zss:

• "user-guide/accessing-zss"
• "user-guide/zss-configuration-1",

zis:

• "user-guide/using-multiple-zis-instances",

apps:

• "user-guide/app-plugin-configuration",
• "user-guide/setting-up-terminal-app-plugins",

administration:

• "user-guide/controlling-access-to-apps",
• "user-guide/controlling-access-to-dataservices",
• "user-guide/customizing-security-plugins",
• "user-guide/administering-the-servers-and-plugins-using-an-api",
• "user-guide/configuration-file",
• "user-guide/logging-configuration",
• "user-guide/network-configuration",

[ArooshLele]

Feedback about categorizing pages from Sean is noted. Thank you, Sean. @1000TurquoisePogs
@ArooshLele @gauravs-20 The Advanced Application Framework Configuration page is now divided into child pages for now. Further to Sean's feedback, I'll investigate the technical aspect of how to bunch the child pages under the related tabs and then open another Pull Request to do so.