feat(rotatingMachine): resolve supplier+type from asset registry, drop denormalized fields

specificClass._setupCurves now calls assetResolver.resolveAssetMetadata
to derive supplier/type/units from the model id, instead of trusting
denormalized fields on the node config. If the model isn't in the
registry, installs a null-predictor stub and logs a clear "pick a model
from the asset menu" error rather than crashing.

rotatingMachine.html: defaults block trimmed (supplier/category/assetType
were stale copies of registry data).

Tests:
- New test/basic/assetMetadata.basic.test.js covers the registry-resolve
  path and the missing-model fallback.
- nodeClass-config / error-paths / nodeClass-routing / factories /
  abort-deadlock fixtures updated to the trimmed asset shape.
- 209/209 tests pass.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

test/helpers/factories.js

@@ -11,10 +11,11 @@ function makeMachineConfig(overrides = {}) {
     functionality: {
       positionVsParent: 'atEquipment',
     },
+    // Post-AssetResolver: only model + unit + tagCode/uuid are saved on the
+    // node. supplier/category/type are derived from the registry. Keeping
+    // legacy fields in the factory would trip the strict-cutover guard in
+    // nodeClass.buildDomainConfig.
     asset: {
-      supplier: 'hidrostal',
-      category: 'machine',
-      type: 'pump',
       model: 'hidrostal-H05K-S03R',
       unit: 'm3/h',
       curveUnits: {