[index patterns] index pattern create modal

[mattkime]

Summary

Index pattern creation modal - create index patterns from any kibana app. Initial implementation in index pattern management.

Closes #84725

To test

• Go to index pattern management
  • Without any data
  • With data but without index patterns
• Click 'Create index pattern'
  • Things should be familiar from here, similar to existing index pattern creation UI

---

Test with index w/o a time field -

create an index without a time field -

PUT my-index-000001/_doc/1?refresh
{
  "my_id": "1",
  "email": "billgates@ms.com"
}

---

Test with a rollup index

• Install ecommerce sample data
• Go to Management / Rollup Jobs and create a new rollup job

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[alexfrancoeur]

@mattkime does this also include an inline editing experience or just create? There are a variety of use cases in which (in context) one might want to modify a field in an index pattern.

[mattkime]

@alexfrancoeur This is just create. We also have the index pattern field editor but it assumes the app provides the field list. If something new is needed lets talk.

[gchaps]

Some minor comments.

[gchaps]

Suggested change

	defaultMessage="The index pattern you've entered doesn't match any indices, data streams, or index aliases.
	defaultMessage="The index pattern you entered doesn't match any data streams, indices, or aliases.

[gchaps]

Is indices correct here? Or is it data streams, indices, or aliases?

[gchaps]

Same comment as above.

[gchaps]

Does something like this work?

Your index pattern doesn't match any data streams, indices, or aliases, but some sources are similar.

[gchaps]

what if this is a data stream or alias? Available matches are below?

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: da62c85
• Storybooks Preview
• Documentation Changes

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
indexPatternEditor	-	104	+104
indexPatternManagement	167	85	-82
total			+22

Async chunks

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

id	before	after	diff
indexPatternEditor	-	169.3KB	+169.3KB
indexPatternManagement	547.4KB	384.6KB	-162.7KB
total			+6.6KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
data	791.1KB	791.3KB	+228.0B
indexPatternEditor	-	21.0KB	+21.0KB
indexPatternManagement	19.2KB	6.9KB	-12.3KB
total			+8.9KB

Unknown metric groups

API count

id	before	after	diff
core	2454	2455	+1
data	3713	3721	+8
total			+9

API count missing comments

id	before	after	diff
core	1165	1166	+1
data	3195	3203	+8
total			+9

async chunk count

id	before	after	diff
indexPatternEditor	-	2	+2

History

• 💔 Build #143422 failed 0f8caa4
• 💚 Build #143364 succeeded 02d00fa
• 💚 Build #143354 succeeded df77a3a
• 💚 Build #143255 succeeded f1b8093
• 💔 Build #143248 failed c9d6835

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

[kibanamachine]

💔 Backport failed

Status	Branch	Result
❌	7.x	Commit could not be cherrypicked due to conflicts

To backport manually run:
node scripts/backport --pr 101853