Update policy docs

What does this MR do?

First change is to upgrade paths. review app link

• There's a 12.0.12 release, so the upgrade paths documentation should be updated from 12.0.9
• Added an example from 9.x to 12.x so there's a canned example for when customers ask
• Clarified the statement around stopping at 12.0.x, and made it forward looking for 13.0.x

Contributor docs - review app link

• Handbook now documents (MR) the difference between bugs and feature requests - linked to it.

Related issues

Author's checklist

• Follow the Documentation Guidelines and Style Guide.
• If applicable, update the permissions table.
• Link docs to and from the higher-level index page, plus other related docs where helpful.
• Apply the documentation label.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

• Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

• Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
2. Ensure a release milestone is set.
3. If there has not been a technical writer review, create an issue for one using the Doc Review template.