Node Dependencies Architecture Verification

[cyaiox]

Is your feature request related to a problem? Please describe.
Currently, scenes managed by the Creator Hub allow users to install Node.js dependencies manually. This can lead to inconsistencies where users may:

• Use different Node.js versions or different package managers.
• Install dependencies incompatible with the product's supported architecture or runtime environment.
• Encounter unexpected errors due to mismatched dependency versions or architectures.

Although we already have a process to install Node.js dependencies and verify outdated dependencies, there is no step to ensure that the installed dependencies align with the Creator Hub's supported Node.js version, npm version, and architecture. This lack of verification risks dependency incompatibility and runtime errors.

Describe the solution you'd like
Introduce a new step in the dependency installation process to verify the architecture and integrity of installed Node.js dependencies. This step should:

• Ensure the installed dependencies are compatible with the Creator Hub's supported architecture (e.g., x64, arm64).
• Reinstall the Node.js dependencies if there are dependencies with mismatched architecture.
• Integrate seamlessly into the existing flow alongside the outdated dependency verification.

Describe alternatives you've considered

• Relying on users to manually adhere to version and architecture requirements: This approach is error-prone and inconsistent.
• Including stricter documentation on supported Node.js and npm versions: While helpful, it doesn't enforce adherence or prevent issues at runtime.

Additional context
This enhancement will provide a robust mechanism to maintain consistency across scenes managed by the Creator Hub, reducing potential runtime errors and improving user experience.