Update Org PR template description

[orezi]

Reference

SPHER-6434

Purpose

To give more details regarding risk classification and set reasonable defaults

Detailed description

Link to change management doc containing risk classification.

Risk classification

• Low — isolated and easily reversible; no security or data-handling impact
• Medium — touches shared components or user-facing behaviour; contained blast radius
• High — security/data-handling, schema/data migrations, infrastructure, or wide blast radius

Impact areas (tick all that apply):

• Security / authentication / authorization
• Data handling / privacy
• Availability / performance
• Public API or other breaking change
• None of the above

Testing

Markdown renders in Dillinger.io

Change monitoring

Ensure no broken links after merge

Rollback

Revert this commit

Manual changes

None

[shillberry]

I would say testing is not always handled by automation, especially if manual tests outside of the repo are required. But the default makes sense, and manual checks can be incorporated elsewhere in the description.