[data views] Enforce uniqueness by name instead of index pattern

[mattkime]

Summary

Data views can now be referenced by their name instead of their index pattern string. In the past, index pattern strings had to be unique since thats the way they were specified in the UI. Now we should keep their names unique instead of their index pattern strings.

Closes #135454

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

[ppisljar]

will this enforce uniqueness of names across spaces as well ?

[mattkime]

@ppisljar No, at least I don't see a reason to enforce uniqueness across spaces, just within them.

[ppisljar]

LGTM

[pgayvallet]

LGTM, one NIT and one request

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 0426d18
• Storybooks Preview

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
dataViewEditor	30.7KB	30.8KB	+166.0B

Saved Objects .kibana field count

Every field in each saved object type adds overhead to Elasticsearch. Kibana needs to keep the total field count below Elasticsearch's default limit of 1000 fields. Only specify field mappings for the fields you wish to search on or query. See https://www.elastic.co/guide/en/kibana/master/development-plugin-saved-objects.html#_mappings

id	before	after	diff
index-pattern	3	4	+1

History

• 💚 Build #57612 succeeded 5c2c1ad
• 💔 Build #57603 failed 480c1de
• 💔 Build #57590 failed 23f5d9c
• 💔 Build #57249 failed b6fd2af
• 💔 Build #57240 failed e4cf00e
• 💔 Build #57229 failed c382f0e

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream