Update docs to point towards Standard V2

[puneetsarna]

Now that we have the Standard plan officially
retired, we should update our docs with the same
information and point users to migrate over to it.

Proposed changes

Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:

Problem: Give a brief overview of the problem or feature being addressed.

Solution: Explain the approach you took to implement the solution, highlighting any significant design decisions or
considerations.

Testing: Describe any testing that you did.

Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.

If this PR addresses an issue on GitHub, ensure that you link to it here:

Closes #ISSUE

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

• I have read the contributing guidelines
• I have signed the F5 Contributor License Agreement (CLA)
• I have rebased my branch onto main
• I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
• I have ensured that the commit messages adhere to Conventional Commits
• I have ensured that documentation content adheres to the style guide
• If the change involves potentially sensitive changes¹, I have assessed the possible impact
• If applicable, I have added tests that prove my fix is effective or that my feature works
• I have ensured that existing tests pass after adding my changes
• If applicable, I have updated README.md and CHANGELOG.md

Footnotes

1. Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩

[russokj]

Just one suggestion, otherwise looks good.

[JTorreG]

no issues from a documentation point of view but the comments about the Standard V2 wording should be addressed

[russokj]

@JTorreG / @jputrino - This MR is requiring two approvals, but I cannot approve it. Does it require two approvals from the doc team? If so, we need to make that just one approval. Ideally, it should require 1 from the dev team and 1 from the docs team (but with how the repo is organized we may not be able to fine tune which dev team).

In any case, can we get the second approval for this?

[JTorreG]

@JTorreG / @jputrino - This MR is requiring two approvals, but I cannot approve it. Does it require two approvals from the doc team? If so, we need to make that just one approval. Ideally, it should require 1 from the dev team and 1 from the docs team (but with how the repo is organized we may not be able to fine tune which dev team).

In any case, can we get the second approval for this?

Docs changes require 2 DocOps approvals. This is intended.