Roles with legacy "Fleet and Integrations" privilege are malformed

[jportner]

Kibana version:

8.1.0+

Describe the bug:

In older versions of Kibana, "Fleet and Integrations" was a single feature (id: fleet):

Starting in the 8.1.0 release, this feature was renamed to "Integrations" and a separate feature was added for "Fleet" (id: fleetv2):

In this release, both features add a new restriction that requires "All spaces" to be selected, as indicated by the tooltip icons in the second screenshot above.
However, that new restriction was introduced for the existing "Integrations" feature and that is a breaking change.

If an operator created a role prior to 8.1 that breaks this restriction, Kibana doesn't know how to transform the role and subsequently throws an error when viewing the page for that role:

If any users created a role prior to 8.1 that (a) granted access to an explicit list of spaces (not "All spaces") and (b) granted access to the "Fleet and Integrations" (either All or Read), then after upgrading to 8.1 the role page would show an error:

Steps to reproduce:

1. Start with Kibana 8.0
2. Create a role that gives access to the Default space and gives access to Fleet and Integrations (either All or Read)
3. Upgrade Kibana to 8.1

Expected behavior:

This restriction should not be applied to the Integrations feature.

Any additional context:

It appears this restriction was accidentally added in #122347 😓

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[juliaElastic]

I think the reason Integrations and Fleet were both set to requireAllSpaces is that none of Fleet entities are space aware currently (integration policies, agent policies, integration assets).
I understand that currently this is a problem with upgraded clusters, however if we remove requireAllSpaces, Integrations privilege would be allowed to be added for specific spaces, which might be misleading as the privilege will not be restricted to any space. Do we still want to go ahead with the fix? cc @joshdover

[zez3]

This is exactly what I needed for my users to be able to see that they have correctly installed their Agents and that the agent is online.

[zez3]

@joshdover
Do you perhaps know if there is already an enhancement request or feature for space aware Agents in Fleet?
I have the use case with users(tenants like) that are not admins and should not be admins to manage their own Integrations, Agents + pipelines
#74353 (comment)

[joshdover]

@zez3 this is the closest we have: #99116. I think a dedicated issue would be best to describe your use case. This is a common use case I’ve heard about in customer discussions, would be good to start collecting feedback if you don’t mind opening an issue.

[zez3]

@joshdover hopefully I've described my use case the right way
#132559