[Fleet] Inconsistent behavior around "Assets" tab

[kpollich]

On the edge-oblt cluster, most packages report as having "No assets" found in the default space. Some packages have some of their assets showing in the "Assets" tab in integration settings, but not all. We should investigate the inconsistencies and either fix the issue or contextualize why this happens on edge-oblt.

Screenshots

View screenshots

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[hop-dev]

first step would be to check installed_kibana_space_id on the package saved object, then check which space the assets are installed in. For reference was introduced in 8.0.0 #120517

[nchaulet]

I just got pinged on a customer call (with Kibana in 8.2.3) where there is no Assets displayed even if the assets are here, probably something we want to prioritize.

[nchaulet]

I found a way to reproduce that, if you use a non superuser with just the fleet roles

POST /_security/role/test_fleet
{
    "cluster": [],
    "indices": [],
    "applications": [
      {
        "application": "kibana-.kibana",
        "privileges": [
          "feature_fleetv2.all",
          "feature_fleet.all"
        ],
        "resources": [
          "*"
        ]
      }
    ]
  }
POST /_security/user/test
{
    "username": "test",
    "roles": [
      "test_fleet"
    ],
    "password": "changeme", 
    "full_name": "",
    "email": "",
    "metadata": {},
    "enabled": true
  }

Then navigate to an installed integration: No assets