Exclude private workspaces from Changesets publishing

[Copilot]

The Version & Publish workflow was failing because Changesets attempted to publish internal workspaces that should never go to npm. This change aligns the release configuration with the repository’s intended publish surface.

• Release scope

  • remove @node-i3x/app and @node-i3x/demo-embedded from the Changesets fixed-version publish group
  • add both workspaces to the Changesets ignore list so release jobs only publish the four public packages

• Workspace publish metadata

  • mark packages/app and packages/demo-embedded as private: true
  • make the workspace manifests reflect their non-publishable role directly, instead of relying only on workflow behavior

• Regression coverage

  • add a focused test that locks the release contract:
    • fixed-version publishing applies only to core, opcua-connector, pseudo-session-connector, and rest-server
    • app and demo-embedded remain private

{
  "fixed": [[
    "@node-i3x/core",
    "@node-i3x/opcua-connector",
    "@node-i3x/pseudo-session-connector",
    "@node-i3x/rest-server"
  ]],
  "ignore": [
    "@node-i3x/app",
    "@node-i3x/demo-embedded"
  ]
}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[erossignon]

App should now be public

[erossignon]

- "private": true,
+ "private": false,

[erossignon]

demo-embeddedshould now be public

[erossignon]

- "private": true,
+ "private": false,

[erossignon]

- "private": true,
+ "private": false,

[erossignon]

- "private": true,
+ "private": false,