Search profiler functional test -- using "test_user" with limited rol…

…e. (#69841)

* using test_user with limited read permission to search profiler test

* gitcheck

* search profiler test using test_user

x-pack/test/functional/apps/dev_tools/searchprofiler_editor.ts

@@ -12,15 +12,21 @@ export default function ({ getPageObjects, getService }: FtrProviderContext) {
   const testSubjects = getService('testSubjects');
   const aceEditor = getService('aceEditor');
   const retry = getService('retry');
+  const security = getService('security');
 
   const editorTestSubjectSelector = 'searchProfilerEditor';
 
   describe('Search Profiler Editor', () => {
     before(async () => {
+      await security.testUser.setRoles(['global_devtools_read']);
       await PageObjects.common.navigateToApp('searchProfiler');
       expect(await testSubjects.exists('searchProfilerEditor')).to.be(true);
     });
 
+    after(async () => {
+      await security.testUser.restoreDefaults();
+    });
+
     it('correctly parses triple quotes in JSON', async () => {
       // The below inputs are written to work _with_ ace's autocomplete unlike console's unit test
       // counterparts in src/legacy/core_plugins/console/public/tests/src/editor.test.js

x-pack/test/functional/config.js

@@ -231,6 +231,17 @@ export default async function ({ readConfigFile }) {
           ],
         },
 
+        global_devtools_read: {
+          kibana: [
+            {
+              feature: {
+                dev_tools: ['read'],
+              },
+              spaces: ['*'],
+            },
+          ],
+        },
+
         //Kibana feature privilege isn't specific to advancedSetting. It can be anything. https://github.com/elastic/kibana/issues/35965
         test_api_keys: {
           elasticsearch: {