Fix assertion messages in SubscriptionData_MockHTTP test class

- Add assertion messages to System.assertEquals calls - Follows Apex best practice: assertions should include descriptive messages - Improves test failure diagnostics

Author: AndyHaas

flow_action_components/AnalyticManagementAPI/force-app/main/default/classes/SubscriptionData_MockHTTP.cls

@@ -25,8 +25,8 @@ global with sharing class SubscriptionData_MockHTTP implements HttpCalloutMock {
  'services/data/' + API_VERSION + '/analytics/' + 
  'notifications?source=lightningReportSubscribe');
  req.setMethod('GET');
- System.assertEquals(expectedEndpoint, req.getEndpoint());
- System.assertEquals('GET', req.getMethod());
+ System.assertEquals(expectedEndpoint, req.getEndpoint(), 'Endpoint should match expected value');
+ System.assertEquals('GET', req.getMethod(), 'HTTP method should be GET');
 
  // Create a fake response
  HttpResponse res = new HttpResponse();