[Logs App] [Metrics App] Remove unnecessarily mapped fields from saved object types

[jasonrhodes]

Based on #43673, we should try to reduce the number of mapped fields in our saved object definitions. If we don't need to search on or aggregate fields saved in our saved objects mapping, we can remove them from the mapping altogether to save on the number of fields that count towards the 1000 field limit per index for the .kibana index.

We need to understand the other consequences of doing this, such as ES validation, etc. See the description here: #43673

Example:

diff --git a/x-pack/plugins/infra/server/lib/sources/saved_object_type.ts b/x-pack/plugins/infra/server/lib/sources/saved_object_type.ts
index 11db18d6bf7..9278c34b088 100644
--- a/x-pack/plugins/infra/server/lib/sources/saved_object_type.ts
+++ b/x-pack/plugins/infra/server/lib/sources/saved_object_type.ts
@@ -17,73 +17,11 @@ export const infraSourceConfigurationSavedObjectType: SavedObjectsType = {
     importableAndExportable: true,
   },
   mappings: {
+    dynamic: false,
     properties: {
       name: {
         type: 'text',
       },
-      description: {
-        type: 'text',
-      },
-      metricAlias: {
-        type: 'keyword',
-      },
-      logAlias: {
-        type: 'keyword',
-      },
-      inventoryDefaultView: {
-        type: 'keyword',
-      },
-      metricsExplorerDefaultView: {
-        type: 'keyword',
-      },
-      fields: {
-        properties: {
-          container: {
-            type: 'keyword',
-          },
-          host: {
-            type: 'keyword',
-          },
-          pod: {
-            type: 'keyword',
-          },
-          tiebreaker: {
-            type: 'keyword',
-          },
-          timestamp: {
-            type: 'keyword',
-          },
-        },
-      },
-      logColumns: {
-        type: 'nested',
-        properties: {
-          timestampColumn: {
-            properties: {
-              id: {
-                type: 'keyword',
-              },
-            },
-          },
-          messageColumn: {
-            properties: {
-              id: {
-                type: 'keyword',
-              },
-            },
-          },
-          fieldColumn: {
-            properties: {
-              id: {
-                type: 'keyword',
-              },
-              field: {
-                type: 'keyword',
-              },
-            },
-          },
-        },
-      },
     },
   },
   migrations: {

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[weltenwort]

So far we don't query by any of those fields AFAIK.