Add nap5 prerequisites

[zahava-brown]

Proposed changes

Checklist

Before sharing this pull request, I completed the following checklist:

• I read the Contributing guidelines
• My branch adheres to the Git conventions
• My content changes adhere to the F5 NGINX Documentation style guide
• If my changes involve potentially sensitive information¹, I have assessed the possible impact
• I have waited to ensure my changes pass tests, and addressed any discovered issues

Footnotes

1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

[ADubhlaoich]

There is absolutely no context around what this new document has been created for, or what problem it is attempting to solve.

Every single deployment document already has a "Before you begin" section which includes all of this detail, and any logical links between this page and others are at the very bottom.

This entire page is redundant with the detail on the existing pages, meaning that a user will read through all possible requirements for any possible deployment even if they are only interested in one, only to come across the exact same set of requirements for their desired deployment at the top of the actual deployment page.

This is a pattern that does not exist in any product documentation for the rest of the NGINX portfolio.

[zahava-brown]

There is absolutely no context around what this new document has been created for, or what problem it is attempting to solve.

Every single deployment document already has a "Before you begin" section which includes all of this detail, and any logical links between this page and others are at the very bottom.

This entire page is redundant with the detail on the existing pages, meaning that a user will read through all possible requirements for any possible deployment even if they are only interested in one, only to come across the exact same set of requirements for their desired deployment at the top of the actual deployment page.

This is a pattern that does not exist in any product documentation for the rest of the NGINX portfolio.

The changes are part of an internal ticket to improve nap5 prerequisite documentation. Right now it is all 1 page and with the help of @ADubhlaoich will be integrated into existing pages