Fixes #5105; For the Sitemap component, don't hardcode root as navigation action path

[tiberiuichim]

The plone.restapi navigation endpoint will compute a navigation root from a context path, but the problem is that Volto will trigger the navigation endpoint either on root or on the lang folder.

https://github.com/plone/plone.restapi/blob/ed070e0769c4ac3efda05448db8846f61dae255c/src/plone/restapi/services/navigation/get.py#L40

https://github.com/plone/volto/blob/4523b13d6586891b9dad7db1caedaab5f6f7dd4b/src/components/theme/Sitemap/Sitemap.jsx#L115C21-L115C21

volto/src/actions/navigation/navigation.js

Line 21 in 4523b13

path: `${url}/@navigation${

[netlify]

✅ Deploy Preview for volto canceled.

Name	Link
🔨 Latest commit	74d5e5a
🔍 Latest deploy log	https://app.netlify.com/sites/volto/deploys/64e348c2146dff0008840001

[cypress]

Passing run #6928 ↗︎

0

553

20

0

0

Details:

Add newsfile
Project: Volto	Commit: 74d5e5a2d3
Status: Passed	Duration: 12:40 💡
Started: Aug 21, 2023 11:25 AM	Ended: Aug 21, 2023 11:37 AM

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[erral]

this should also be taken into account in #3537

[erral]

@tiberiuichim revisiting this PR in order to do a more complete use of the navroot endpoint (#3537), I see quite easy to change the usage of isMultilingual and toBackendLang here and replace them with the navroot.

But I don't get at all how this could be done for the SSR part (I guess, that's what it's done in the asyncConnect part, right?)

Perhaps, if #3537 is merged, I can prepare a PR bringing the usage of @navroot here and we can discuss there how to bring it also to the SSR part.