Fix TypeMapAssemblyTarget xref (remove extra Attribute suffix)

Co-authored-by: AaronRobinsonMSFT <30635565+AaronRobinsonMSFT@users.noreply.github.com>

Author: Copilot

xml/System.Runtime.InteropServices/TypeMapAssociationAttribute`1.xml

@@ -62,7 +62,7 @@ Finally, if the trimming tool determines that it's impossible to retrieve a <xre
 > Conflicting key/value mappings are not allowed.
 
 > [!NOTE]
-> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it's not guaranteed that the <xref:System.Runtime.InteropServices.TypeMapAttribute%60%601>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute%60%601>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTargetAttribute%60%601> attributes are present in the final image after a trimming tool has been run.
+> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it's not guaranteed that the <xref:System.Runtime.InteropServices.TypeMapAttribute%60%601>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute%60%601>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTarget%60%601> attributes are present in the final image after a trimming tool has been run.
 
       ]]></format>
     </remarks>

xml/System.Runtime.InteropServices/TypeMapAttribute`1.xml

@@ -65,7 +65,7 @@ Many of these instructions can be passed a generic parameter. In that case, the
 > Conflicting key/value mappings are not allowed.
 
 > [!NOTE]
-> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it's not guaranteed that the <xref:System.Runtime.InteropServices.TypeMapAttribute%60%601>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute%60%601>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTargetAttribute%60%601> attributes are present in the final image after a trimming tool has been run.
+> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it's not guaranteed that the <xref:System.Runtime.InteropServices.TypeMapAttribute%60%601>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute%60%601>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTarget%60%601> attributes are present in the final image after a trimming tool has been run.
 
       ]]></format>
     </remarks>