[App Search] Split CrawlerLogic from CrawlerOverviewLogic

[byronhulcher]

Summary

This moves 99% functionality from out of the logic powering the CrawlerOverview view out into a more general logic for all Crawler views, including CrawlerSingleDomain. All thats left in CrawlerOverviewLogic is the deleteDomain action. The rest has been migrated verbatim to the new CrawlerLogic. I've also updated related Crawler components to use the correct logic.

In the near future (following this PR) I'm going to do a big re-org of the crawler directory, to make clearer what components are shared or unique to each crawler view.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[kibanamachine]

💚 Build Succeeded

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

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
enterpriseSearch	1472	1473	+1

Async chunks

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

id	before	after	diff
enterpriseSearch	2.2MB	2.2MB	+140.0B

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

cc @byronhulcher

[orhantoy]

I'm not a Kea expert but the changes look pretty safe to me.

I was wondering why deleteDomain also wasn't moved so we could drop that logic file completely?

[byronhulcher]

@orhantoy Could you approve? Jason is on PTO until Monday and I'd like to get this into the next 7.15 BC ASAP

I was wondering why deleteDomain also wasn't moved so we could drop that logic file completely?

Since that logic is specific to the CrawlerOverview page, I wanted to keep it there. The CrawlerSingleDomain page has its own deleteDomain action, it didn't make sense to me to have one higher than the other in the hierarchy.

[orhantoy]

Since that logic is specific to the CrawlerOverview page, I wanted to keep it there. The CrawlerSingleDomain page has its own deleteDomain action, it didn't make sense to me to have one higher than the other in the hierarchy.

Makes sense; thanks for the explanation 💯

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.15
✅	7.x

The backport PRs will be merged automatically after passing CI.