[UnifiedDataTable] Add display option to hide / show field token in header cells

[kertal]

In #167179 we introduced field tokens to the UnifiedDataTable grid header. Now we should make it configureable, to optimize for use cases there this additional information is redundant.

• In UI by adding a new configuration toggle to the Display options
• On component level, allowing consumers to set the default value

If we are able to move forward with adding tokens to the Document column, this configuration can also be used for this:
#164634

Open question

• We need to clarify, if this setting needs to be persisted in saved search in Discover, like all other settings in the Display options popover, or should it persisted e.g. in Browser localStorage

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[MichaelMarcialis]

We need to clarify, if this setting needs to be persisted in saved search in Discover, like all other settings in the Display options popover, or should it persisted e.g. in Browser localStorage

@kertal: That's a tricky one. On one hand, it would be nice to have all preferences within that popover be consistent in how they are implemented and persisted. As such, including it as part of the saved object would make sense for that consistency.

On the other hand, while items like column width, row height, and sample size make sense to persist at the saved object level (and showing for all users), other more subjective preferences like toggling row stripes and field type tokens might be better suited as an assistive option for individual users and persisted across all Discover sessions for that particular user (and not showing for those that don't want them).

I suppose for now, my recommendation would be to stick with the consistent approach, and re-evaluate if we get user feedback to the contrary. CCing @andreadelrio as well, in case she has thoughts.

[kertal]

I suppose for now, my recommendation would be to stick with the consistent approach, and re-evaluate if we get user feedback to the contrary. CCing @andreadelrio as well, in case she has thoughts.

thx for your feeback. this approach matches very well with what we discussed in our team sync. I'd suggest to icebox this, and to unfreeze when needed

[kertal]

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.