[SecuritySolution] update sourcer messages

[angorayc]

Summary

issue: #121984

1. Create a timeline template with auditbeat-* in timeline sourcerer

2. Go to Kibana advanced settings, and remove auditbeat-* from Security Solution's Elasticsearch indices

3. Refresh the page and open the timeline template you just created, the call out should say
   This timeline template is out of date with the Security Data View

We have preserved your timeline template by creating a temporary data view. If you'd like to modify your data, we can add the missing index patterns to the Security Data View. You can also manually select a data view here.

5. Go back to Kibana advanced settings and reset the indices to default settings.

6. Start over again from step 1, but create a timeline instead. When opening the sourcerer of timeline, it should say
   This timeline is out of date with the Security Data View

We have preserved your timeline by creating a temporary data view. If you'd like to modify your data, we can add the missing index patterns to the Security Data View. You can also manually select a data view here.

sourcerer.mp4

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
• Unit or functional tests were updated or added to match the most common scenarios

[angorayc]

FormattedMessage doesn’t accept its props to be variables (The build will fail and complain about this), so I created components to return messages by timeline type.

[stephmilovic]

LGTM, thanks for the fix!

[YulNaumenko]

LGTM

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 81281f0
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	2782	2783	+1

Async chunks

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

id	before	after	diff
securitySolution	4.8MB	4.8MB	+2.8KB

History

• 💔 Build #37315 failed 52320d2
• 💔 Build #37275 failed 7416f7a
• 💔 Build #35848 failed e5cc68e

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

cc @angorayc

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.1
✅	8.2

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation