Docs: Format NGINX configuration table.

[Gacko]

What this PR does / why we need it:

Formats the configuration options table using the Markdown Table Formatter plugin for Visual Studio Code and thus aligns it across branches and simplifies git diff.

I did not change the values, only their format.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added unit and/or e2e tests to cover my changes.
• All new and existing tests passed.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Gacko

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• docs/OWNERS [Gacko]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Gacko]

/triage accepted
/kind documentation
/priority backlog
/cc @longwuyuan

[strongjz]

The root problem is probably with the docs generation script, so a new release will reset these changes.

[Gacko]

Actually not. This got introduced by a user. They diff between release-v1.10 and release-v1.11 and the release process does not touch this.