Add deprecation warning to Uri.UserEscaped property documentation (#11467)

* Initial plan for issue

* Add deprecation warning to Uri.UserEscaped property documentation

Co-authored-by: gewarren <[email protected]>

* Update xml/System/Uri.xml

* Update xml/System/Uri.xml

* Remove misleading "always false" claim from Uri.UserEscaped documentation

Co-authored-by: gewarren <[email protected]>

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: gewarren <[email protected]>

Author: Copilot

xml/System/Uri.xml

@@ -6030,7 +6030,8 @@ The following examples show a URI and the results of calling <xref:System.Uri.Ge
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Uri.UserEscaped%2A> property is set to `true` to indicate that the string used to create the <xref:System.Uri> instance was completely escaped before it was passed to the constructor; that is, the `dontEscape` parameter of the constructor call was set to `true`.
+
+The <xref:System.Uri.UserEscaped> property was originally designed to indicate that the string used to create the <xref:System.Uri> instance was completely escaped before it was passed to the constructor; that is, the `dontEscape` parameter of the constructor call was set to `true`. However, since the `dontEscape` parameter is now obsolete, this property is deprecated and shouldn't be used.
 
 ## Examples
  The following example creates a <xref:System.Uri> instance and determines whether it was fully escaped when it was created.