Add config to set allow_no_indices when getting fieldcap

[seongpyoHong]

Is your feature request related to a problem? Please describe.

Background

Opensearch & Dashboard Version: 2.12.0

I use Cross Cluster Search with Remote Cluster settings.

• Cluaster
  • CCS Cluster: Cluster for Cross Cluster Search
  • Data1 / Data2 Cluster: Cluster to store indices
• Index Location
  • index1: Index: exists in Data1
  • index2: index: exists in Data2

Problem

In a situation where you are creating an Index Pattern for a Remote Cluster, the following issue occurs.

• When using the wildcard expression *:index1*, *:index2*, the Time field is not retrieved correctly.
• This is because an error occurs when requesting to get the field cap. The reason for the error is that Opensearch Dashboard does hardcoding the allow_no_indices option to false when executing the Opensearch Field Cap API. :

  OpenSearch-Dashboards/src/plugins/data/server/index_patterns/fetcher/lib/opensearch_api.ts

  Lines 86 to 99 in 9ec9a67

  	export async function callFieldCapsApi(
  	callCluster: LegacyAPICaller,
  	indices: string[] | string,
  	fieldCapsOptions: { allowNoIndices: boolean } = { allowNoIndices: false }
  	) {
  	try {
  	return (await callCluster('fieldCaps', {
  	index: indices,
  	fields: '*',
  	ignoreUnavailable: true,
  	...fieldCapsOptions,
  	})) as FieldCapsResponse;
  	} catch (error) {
  	throw convertOpenSearchError(indices, error);

*Describe the solution you'd like

This needs to be set to config so that the allow_no_indice option can be changed.

Describe alternatives you've considered

Since the default value of allow_no_indices in the Opensearch API is true, we also set it to true in Dashboard.

Additional context

• Field Capabilities API : https://www.elastic.co/guide/en/elasticsearch/reference/current/search-field-caps.html