StaticRootPlugin does not work with non-empty or non-root namespaces

[ozyx]

Summary

Creating a StaticRoot will fail to handle properly objects with a non-empty namespace (any non-default namespace), or non-root namespaces (a namespace that differs from the exported root namespace).

Notice the Missing: [object Object] items in the tree after using this JSON with the StaticRootPlugin. This is due to the plugin overwriting composition items with malformed identifiers if they have a non-empty or non-root namespace.

Expected vs Current Behavior

The StaticRootPlugin should be able to handle and remap objects with non-root and non-empty namespaces

Steps to Reproduce

1. Start openmct-yamcs with StaticRootPlugin configured with the attached test json
2. Notice that objects in composition don't load correctly

Environment

• Open MCT Version: 2.2.2-SNAPSHOT
• Deployment Type: openmct-yamcs
• OS: MacOS
• Browser: Chrome

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

Additional Information

[ozyx]

Testing Instructions

1. Download and extract the attached JSON
2. Install the plugin into openmct-yamcs with the following code:

      // Also install the Clock plugin since the JSON includes one :)
      openmct.install(openmct.plugins.Clock({ enableClockIndicator: true }));
      openmct.install(openmct.plugins.StaticRootPlugin({
          namespace: 'test-namespace',
          exportUrl: './nonemptynamespace.json'
      }));

3. Ensure no console errors, and that the JSON is imported correctly as a static root.

[akhenry]

Verified fixed.