Remove recursive plugin status in meta field

[joshdover]

Summary

Fixes #100202

Depending on how a plugin implements their custom status check, it's possible for our status log messages to explode in size due to how the default status summaries rollup all of their dependencies' statuses in a recursive, cascading manner. This PR changes the default status summary to only include the names of the affected dependencies, rather than their entire status check which is already available in the full status object.

Here's the change for an individual plugin's default status object:

Before

{
  "level": "unavailable",
  "summary": "[2] services are unavailable",
  "detail": "See the status page for more information",
  "meta": {
    "affectedServices": {
      "dependencyA": {
        "level": "unavailable",
        "summary": "dependencyB is unavailable",
        "meta": {
          "affectedServices": {
            "dependencyB": {
              "level": "unavailable",
              "summary": "Something isn't working"
            }
          }
        }
      },
      "dependencyB": {
        "level": "unavailable",
        "summary": "Something isn't working"
      }
    }
  }
}

After

{
  "level": "unavailable",
  "summary": "[2] services are unavailable",
  "detail": "See the status page for more information",
  "meta": {
    "affectedServices": ["dependencyA", "dependencyB"]
  }
}

Checklist

Delete any items that are not applicable to this PR.

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

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[jportner]

@joshdover WDYT about backporting this to 7.14.1?

[kibanamachine]

💚 Build Succeeded

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

Metrics [docs]

✅ unchanged

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

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.14
✅	7.x

The backport PRs will be merged automatically after passing CI.