[APM] Fix cypress memory issue due to log panel (#167623)

## Summary

Recent [EUI bump](#166868) from
v88.3.0 to v88.5.0 increased the memory usage significantly. Due to
which Cypress Tests started failing due to browser crashing with memory
limits. EUI team has been informed about this.

As reverting EUI is not a simple change, disabling the Cypress Log panel
solves the problem for now. Details can be found
[here](cypress-io/cypress#27415 (comment))

This brings change to how we run the Cypress Test in Head Mode

## Before


![image](https://github.com/elastic/kibana/assets/7416358/12a92c64-2e31-4423-8e8a-94a311757bd7)

## After

![image
(1)](https://github.com/elastic/kibana/assets/7416358/d3a522c9-66e8-497c-b046-32a6c866b600)

x-pack/plugins/apm/ftr_e2e/cypress/e2e/settings/agent_configurations.cy.ts

@@ -123,7 +123,7 @@ describe('Agent configuration', () => {
       .click({ force: true })
       .type('All');
 
-    cy.get('mark').contains('All').click();
+    cy.get('mark').contains('All').click({ force: true });
     cy.contains('Next step').click();
     cy.contains('Service name All');
     cy.contains('Environment All');

x-pack/plugins/apm/ftr_e2e/cypress_test_runner.ts

@@ -76,6 +76,7 @@ export async function cypressTestRunner({ getService }: FtrProviderContext) {
       ES_NODE: esNode,
       ES_REQUEST_TIMEOUT: esRequestTimeout,
       TEST_CLOUD: process.env.TEST_CLOUD,
+      NO_COMMAND_LOG: 1, // Temp fix, With Cypress 13, this might not be required https://github.com/elastic/kibana/pull/162383
     },
   });