[Logs Explorer] Ensure compatibility with data view caching

[weltenwort]

📓 Summary

#168910 adds caching of the field list to data views. When on-boarding new datasets we rely on new data becoming available, so we need to ensure the cache doesn't break that. We should also consider adding a means for the user to manually invalidate the cache.

✔️ Acceptance criteria

• The data view caching doesn't break the on-boarding flow.
• There is a way for the user to manually refresh the field list.

🎨 Mock-ups

🚧 TODO

[weltenwort]

@isaclfreire could you please help us with mock-ups for the manual field refresh? 😇

[elasticmachine]

Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)

[kertal]

QQ: ist this still needed? UnifiedFieldList takes care of automatically adding new fields and also refreshing the cached data view in this case, it was merged recently, and this issue was created in November, so maybe this is already resolved?

PR #172329

[gbamparop]

Hi @kertal, this issue is mostly to double check that the changes introduced by #172329 work as expected with logs explorer. We might add some automated tests for some cases too.

[thomheymann]

@weltenwort Does this issue #172329 resolve your concerns around refreshing fields or do we still require a manual refresh button? Could you also let me know what the dataset onboarding flow is you mention so that I can verify whether this works as expected?

[thomheymann]

I have tested the boarding flow locally. New dataset and its fields show up correctly as part of the onboarding journey.