[BUG] resx resource not used correctly when applying template

Expected behaviour
On a multilingual site, when using Invoke-PnPSiteTemplate all translatable elements from the resx resource files should be applied, including the navigation nodes.

Actual behaviour
All translations are applied except for the navigation nodes, these are only applied in the sites default language.

Steps to reproduce behaviour

1. Create a team site without M365 group with default language Dutch
2. Connect to the new site with PnP.PowerShell
3. Execute Invoke-PnPSiteTemplate with nav.xml
4. Go to the site using a browser that is in English, the navigation will be in Dutch

Which operating system/environment are you running PnP PowerShell on?
We experience this bug in 2 environments

1. On Azure in a C# project using PnP.Framework version 1.13.0
2. Locally using PowerShell 7 and PnP PowerShell 2.5.0; I tried downgrading to 2.4.0 and 2.3.0 but the bug persists.

Extra Info
We have 3 tenants, in our test tenant the navigation nodes are created as expected... But in our quality assurance
and production tenants they are not.

Files (added .txt to be able to upload them, remove this when executing)
nav.xml.txt
NAV.nl-NL.resx.txt
NAV.en-US.resx.txt

Start with the Invoke-PnPSiteTemplate entry point and reproduce the issue using the attached nav.xml, NAV.nl-NL.resx, and NAV.en-US.resx files. Trace how navigation nodes consume the resx translations, compare behavior across the default and browser languages, and verify that multilingual navigation is applied consistently in the relevant tests or reproduction.