reorder table and topics to group required config for API ML

[janan07]

Describe your pull request here: reorder table and topics to group required config for API ML

List the file(s) included in this PR: configure-zos-system (v2.18), configuration-client-certificates, authenticating-with-client-certificates

After creating the PR, follow the instructions in the comments.

[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]

📁 The PR description is missing the file name(s) for the updated content. List all the files included in this PR so this information displays in our Zowe Docs GitHub Slack channel.

If you have addressed this issue already, refresh this page in your browser to remove this comment.

[github-actions]

🚀 Deployed on https://67f3a99390c34434714ebf79--zowe-docs-master.netlify.app

[balhar-jakub]

Even though the certificates we use are x509 we also have x509 as the authentication scheme.

For the authentication scheme you need neither setups. For the client certificate authentication in general you need either one of them.

So maybe something like:
There are two methods to enable client certificate functionality integrated with the SAF:

[balhar-jakub]

Generally be careful with addition of the x509, while it is true that the certificates we support are x509 we also use the term in another way which may confuse people.

[janan07]

The reason behind this addition is that there is a terminology discrepancy between references in Zowe Docs to just client certificates and references in ESZ that describe x.509 client certificates. It should be clear that the certificates are x509 in the Zowe doc if that is where we are sending ESZ customers.

[balhar-jakub]

Ok, Then we should use X.509 as the exact name in the Zowe Docs as well.