Allow the parent window to configure and manage navigation requests

[cstns]

Allow the parent window to configure and manage navigation requests when the NR editor resides in an embedded context/iframe

Description

Related Issue(s)

Checklist

• [ ] I have read the contribution guidelines
• [ ] Suitable unit/system level tests have been added and they pass
• [ ] Documentation has been updated
  • [ ] Upgrade instructions
  • [ ] Configuration details
  • [ ] Concepts
• [ ] Changes flowforge.yml?
  • [ ] Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • [ ] Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

• [ ] Backport needed? -> add the backport label
• [ ] Includes a DB migration? -> add the area:migration label

@closes https://github.com/FlowFuse/nr-launcher/issues/223

[cstns]

Some feedback / input would be appreciated on the interception of the logo click event

[hardillb]

If we are confident that this is it for changes to the theme, then yes, bump the inner package.json.

@sherbastian The top level nr-launcher package.json will get bumped by the release script I mentioned on our call earlier. I will try to remember to point it out in the release huddle on Thursday.

[cstns]

Reverted the v bump, the PR should be good to go. It can be released independently of #3656 without any side effects

[cstns]

@Steve-Mcl, should I do it manually?

[Steve-Mcl]

@Steve-Mcl, should I do it manually?

Yes, just update the value in this PR. The inner package is not published and has no automations.