[Dataset quality] Document column when cross-linking to discover (ela…

…stic#192155)

Relates to
elastic#192072 (comment).

As of now we are redirecting to discover using `message` column which is
not relevant for dataStream types different than logs.

In the current setup we don't have a way to have in discover a column
like Logs explorer `content` column, which could help us to achieve
fallbacks for certain columns. Also is not possible to combine
`Document` column with other columns.

This PR sends columns empty for discover locator which will include at
the end `@timestamp` and `Document` columns.

### Before


https://github.com/user-attachments/assets/75831794-7171-498c-8834-42d0d77d75f7


### After


https://github.com/user-attachments/assets/e5d35f45-f143-482b-aec9-5de794f20961

x-pack/plugins/observability_solution/dataset_quality/public/hooks/use_redirect_link.ts

@@ -183,10 +183,11 @@ const buildDiscoverConfig = <T extends BasicDataStream>({
     dataViewSpec: {
       id: dataViewId,
       title: dataViewId,
+      timeFieldName: '@timestamp',
     },
     query,
     breakdownField,
-    columns: ['@timestamp', 'message'],
+    columns: [],
     filters: [
       buildPhraseFilter(
         {