[data views] allow cross cluster index pattern negation (#147968)

## Summary

The data views api examines comma delimited sections to see if there are
matching indices before fetching the field list. The existing code
checked for index pattern negation - patterns that started with a `-`.
However, it didn't check for this in cross cluster case -
`this_cluster:-kibana*`. The code now handles the cross cluster case
appropriately.

Still, its unclear to me whether this logic is necessary, hence why I
opened #147970 - I was able to
resolve the failed tests most familiar to me but I will need to work
with engineers from other teams to investigate other failures.

Closes #147926

src/plugins/data_views/server/fetcher/index_patterns_fetcher.test.ts

@@ -40,8 +40,8 @@ describe('Index Pattern Fetcher - server', () => {
       .mockResponseOnce(emptyResponse as unknown as estypes.FieldCapsResponse)
       .mockResponse(response as unknown as estypes.FieldCapsResponse);
     // first field caps request returns empty
-    const result = await indexPatterns.validatePatternListActive(['-a', 'b', 'c']);
-    expect(result).toEqual(['-a', 'c']);
+    const result = await indexPatterns.validatePatternListActive(['-a', 'b', 'c', 'a:-b']);
+    expect(result).toEqual(['-a', 'c', 'a:-b']);
   });
   it('Returns all patterns when all match indices', async () => {
     esClient.fieldCaps.mockResponse(response as unknown as estypes.FieldCapsResponse);

src/plugins/data_views/server/fetcher/index_patterns_fetcher.ts

@@ -126,7 +126,7 @@ export class IndexPatternsFetcher {
       patternList
         .map(async (index) => {
           // perserve negated patterns
-          if (index.startsWith('-')) {
+          if (index.startsWith('-') || index.includes(':-')) {
             return true;
           }
           const searchResponse = await this.elasticsearchClient.fieldCaps({