[ML] Anomaly detection job custom_settings improvements

[jgowdyelastic]

Adds Job tags and a general Custom settings to the list of properties listed in a job's expanded row:

Adds the ability to search for job_tags with job_tags:<tag>:<value>
e.g. job_tags:"euid:8015" or job_tags:(euid:8015 or euid:8016) to match multiple tags.

Fixes #101877

cc @randomuserid

• 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 was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[jgowdyelastic]

@elasticmachine merge upstream

[jgowdyelastic]

@elasticmachine merge upstream

[spong]

Checked out locally and verified ML Job Settings UI functions as intended -- Security Solution changes LGTM!

[peteharverson]

Testing this I found an issue with the reloading of expanded rows when the search changes. If you expand a row, edit the search, and then set it back to its previous value, the previously expanded row shows the loading icon which never disappears. Not related to searching for job_tags - also happens with the existing job ID / description based search.

This also happens if you expand a row, go to the next page, and then back to the starting page - there is a loading indicator displayed for the row that was previously expanded.

[peteharverson]

LGTM, although I did find an existing bug in the search functionality with expanded rows.

[jgowdyelastic]

@elasticmachine merge upstream

[jgowdyelastic]

@peteharverson row expansion issue fixed in 8a107a8

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 8a107a8
• Storybooks Preview

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
ml	270	272	+2

Async chunks

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

id	before	after	diff
ml	5.9MB	5.9MB	+1.9KB
securitySolution	6.9MB	6.9MB	+11.0B
total			+1.9KB

Unknown metric groups

API count

id	before	after	diff
ml	274	276	+2

History

• 💚 Build #132050 succeeded 05019e2
• 💚 Build #131527 succeeded 51c9a2b
• 💔 Build #131430 failed caa968b
• 💔 Build #131397 failed 32e638b
• 💔 Build #131376 failed 2d4de2a

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

cc @jgowdyelastic

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.

[randomuserid]

Looks great, all of these searches evaluate true;

job_tags:(euid:8015 or euid:8016)
job_tags:(event.category:authentication)
job_tags:(maturity:experimental)
job_tags:(updated_date:5/12/2021)
job_tags:(version:1)

It looks like a search for author does not evaluate true if a user puts their Twitter handle in the field like this;

job_tags:(author:@randomuserid)

Do we need to escape the @ char somehow? If this isn't going to work, initially, I can ask people to use their GitHub name, if they have one, or their common name, if they don't.

[peteharverson]

Created #104706 to fix the issue for searches using the @ character.