Automate index pattern version conflict tests

[LeeDr]

Describe the feature: New functionality in Kibana protects one user from accidentally clobbering another user's changes to an index pattern. The changes could be popularity (which changes by add/removing fields from the doc view), field formatting, scripted fields, etc.

See: #18937

Describe a specific use case for the feature:
NOTE: I do not think the above PR fixed the potential for version conflicts on any other saved objects. So one user could still clobber another user's change to the config object, saved searches, visualizations, etc.