fix(power-management): Remove remoteproc device constraint example

Remove the example of how to set a device constraint that leaves the
device powered on. This example references the remoteproc driver. In
this driver, the constraint is being set during suspend_late. At that
point in the suspend sequence, no new constraints are being sent to the
DM so this code does not show a device constraint being set correctly.

Signed-off-by: Kendall Willis <k-willis@ti.com>

Author: kwillis01

source/linux/Foundational_Components/Power_Management/pm_sw_arch.rst

@@ -196,11 +196,6 @@ Default constraint is "no constraint", but it can be changed as shown in the exa
 Setting a resume latency constraint impacts the deepest low power mode system can enter.
 The various modes and their latencies are documented here: https://downloads.ti.com/tisci/esd/latest/2_tisci_msgs/pm/lpm.html#tisci-msg-lpm-set-latency-constraint
 
-If a device wants to put a constraint to not be powered-off, it can use the Linux
-QoS framework and set the ``DEV_PM_QOS_RESUME_LATENCY`` equal to 0.
-An example is shown in the following RemoteProc driver:
-https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/remoteproc/ti_k3_r5_remoteproc.c?h=11.00.09#n549
-
 .. note::
 
    The constraints need to be set before each system suspend as DM firmware clears all