BUG: Space admin, doesn't have read privileges to private subsubspace of priave space

[Comoque1]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Using the server-api tests run the following command:npm run test:roleset ./src/functional-api/roleset/user/user.authorization.it-spec.ts , BUT comment first:

// afterAll(async () => {
//   await TestScenarioFactory.cleanUpBaseScenario(baseScenario);
// });

so that the data is not removed
2. Perform the following query with the Space admin:

{
  space(ID: "8d70fcd2-d108-4799-969a-42701fc5c339") {
    settings {
      ...SpaceSettings
    }
    community {
      roleSet {
        roleNames
        usersInRoles(roles: ADMIN) {
          users {
            email
          }
        }
        authorization {
          myPrivileges
        }
      }
    }
    subspaces {
      settings {
        ...SpaceSettings
      }
      community {
        roleSet {
          usersInRoles(roles: ADMIN) {
            users {
              email
            }
          }
          authorization {
            myPrivileges
          }
        }
      }
      subspaces {
        id
        community {
          roleSet {
            roleNames
            usersInRoles(roles: ADMIN) {
              users {
                email
              }
            }
            authorization {
              myPrivileges
            }
          }
        }
        settings {
          ...SpaceSettings
        }
        authorization {
          myPrivileges
        }
      }
    }
  }
}

fragment SpaceSettings on SpaceSettings {
  collaboration {
    allowEventsFromSubspaces
    allowMembersToCreateCallouts
    allowMembersToCreateSubspaces
    inheritMembershipRights
  }
  membership {
    allowSubspaceAdminsToInviteMembers
    policy
    trustedOrganizations
  }
  privacy {
    allowPlatformSupportAsAdmin
    mode
  }
}

3. Error is thrown: "message": "User ([email protected]) does not have credentials that grant 'read-about' access to Space.community with id 'ad179f20-a54f-4a3e-a651-17fcf8d2e948' with authorization: 35d35139-c0d2-49cd-b99e-a92d1465b8a1",
   The space admin doesn't have rights to read community of private subsubspace
   The space member, has rights to read community of private subsubspace

Expected behavior
The space admin has rights to read community of private subsubspace
The space member, doesn't have rights to read community of private subsubspace

Additional context
The issue is unlikely to be reproduced, as we don't expose subsubspace privacy settings on client