IBX-9266: Added REST endpoint loading available site accesses for location

[barw4]

🎫 Issue	IBX-9266

Related PRs:

ibexa/fieldtype-richtext#267

Description:

A new endpoint is exposed as /api/ibexa/v2/siteaccess/load-non-admin-for-location/{locationId} that utilizes the existing SiteaccessResolverInterface that fetches eligible site accesses for a given location.

Example response

{
  "SiteAccessesList": {
    "_media-type": "application/vnd.ibexa.api.SiteAccessesList+json",
    "values": [
      {
        "_media-type": "application/vnd.ibexa.api.SiteAccess+json",
        "name": "__default_site_access__",
        "provider": "Ibexa\\Core\\MVC\\Symfony\\SiteAccess\\Provider\\StaticSiteAccessProvider"
      },
      {
        "_media-type": "application/vnd.ibexa.api.SiteAccess+json",
        "name": "__second_site_access__",
        "provider": "Ibexa\\Core\\MVC\\Symfony\\SiteAccess\\Provider\\StaticSiteAccessProvider"
      },
      {
        "_media-type": "application/vnd.ibexa.api.SiteAccess+json",
        "name": "ger",
        "provider": "Ibexa\\Core\\MVC\\Symfony\\SiteAccess\\Provider\\StaticSiteAccessProvider"
      },
      {
        "_media-type": "application/vnd.ibexa.api.SiteAccess+json",
        "name": "eng",
        "provider": "Ibexa\\Core\\MVC\\Symfony\\SiteAccess\\Provider\\StaticSiteAccessProvider"
      },
      {
        "_media-type": "application/vnd.ibexa.api.SiteAccess+json",
        "name": "ku6\"H",
        "provider": "Ibexa\\Core\\MVC\\Symfony\\SiteAccess\\Provider\\StaticSiteAccessProvider"
      }
    ]
  }
}

For QA:

Documentation:

[alongosz]

Conceptually I think this is the proper placement for the endpoint.
Other remarks:

[alongosz]

This should be site_access and site-access for route name and path respectively. These are separate words. Alternatively SiteAccess which doesn't apply here I think. I know we have mistakes in this codebase for namespaces (it's not consistent, sometimes Siteaccess, sometimes SiteAccess, but here I'd see this as new code, which should be correct.

[alongosz]

My preference here would be SiteAccessList similarly as we refer to it on other places afair and the same as ContentInfoList, LocationList, etc.

[barw4]

The issue is that we also use SiteAccessesList in a lot of places in directly related services, e.g.: https://github.com/ibexa/admin-ui/blob/main/src/lib/Siteaccess/NonAdminSiteaccessResolver.php#L33 (a lot of other places in admin-ui), therefore I wanted to stay consistent with it as I'm directly using this service. But obviously I can change it if you prefer it your way.

[alongosz]

and the same remark for the object itself as in the previous comment.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud