Clarify Azure policy for new-version RequiredStatusChange findings (#542)

* Initial plan

* docs: clarify Azure policy for RequiredStatusChange

Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com>

* docs: remove ambiguity from requiredness change cause

Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com>

* docs: remove redundant RequiredStatusChange guidance

Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com>

* docs: apply requested RequiredStatusChange cause wording

Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com>

* Fix formatting in RequiredStatusChange documentation

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com>

Author: Copilot

docs/rules/1025.md

@@ -2,7 +2,8 @@
 
 **Description**: Checks whether an existing property's `required` status is changed from the previous specification. 
 
-**Cause**: This is considered a breaking change in the same api-version but not breaking in new api-version . 
+**Cause**: Changing an existing property's `required` status is a breaking change in the same api-version.
+In a new api-version, whether the change is breaking depends on its impact on the wire contract and Azure REST API breaking-change policy.
 
 **Example**: `required` status for parameter `b` is changed from `false` to `true` without revising api-version.