Gate sp_PerfCheck LPIM recommendation off Azure MI and AWS RDS

The LPIM check (check_id 4105) only excluded @azure_sql_db from its
firing condition. Azure Managed Instance and AWS RDS both run SQL
Server on managed platforms that don't expose the
LockPagesInMemory user right, so telling the operator to enable LPIM
on those edition/platforms is unactionable noise. The IFI check
immediately below this one (line ~1177) already excludes all three,
so LPIM is just catching up.

Added AND @azure_managed_instance = 0 AND @aws_rds = 0 to the outer
IF gate. On-prem check still fires under the same conditions as before
(memory model = CONVENTIONAL, physical RAM >= 32 GB). Verified the
sproc installs clean and the LPIM finding does not appear on the
test SQL 2022 instance (which has memory model = LOCK_PAGES, so the
check correctly suppresses).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: erikdarlingdata

sp_PerfCheck/sp_PerfCheck.sql

@@ -1134,8 +1134,14 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
     FROM sys.dm_os_sys_info AS osi;
     END;
 
-    /* Check if Lock Pages in Memory is enabled (on-prem and managed instances only) */
+    /* Check if Lock Pages in Memory is enabled.
+       Only on-prem can change LPIM. Azure Managed Instance and AWS RDS
+       both run SQL Server on platforms that don't expose the
+       LockPagesInMemory user right, so flagging them is unactionable
+       noise. Matches the IFI check gate below for consistency. */
     IF  @azure_sql_db = 0
+    AND @azure_managed_instance = 0
+    AND @aws_rds = 0
     AND @has_view_server_state = 1
     BEGIN
         INSERT INTO