fix(plugins): reload updated plugins via version-keyed cache paths

[albanm]

Upgrade @data-fair/lib-node-registry to ^0.7.0 and remove the query-string cache-busting from importPluginModule.

Why: 0.7.0 extracts each plugin version into its own directory, so an updated plugin resolves to a fresh module URL and Node's registry reloads the whole graph naturally — the manual ?imported=<timestamp> cache-bust in the API's prepare flow is no longer needed.

Regression risks:

• Correctness now depends on 0.7.0 giving each plugin version a distinct directory. A plugin re-published with changed code under the same version string would resolve to the same path and be served stale from the long-lived API process (the old cache-bust would have dodged this).
• The API prepare flow can run twice in one save (api/src/processings/router.ts:187); the second import now hits Node's module cache. Safe as long as the path is identical across both runs within a save, which it should be.
• Worker is unaffected — it never used cache-busting and runs each task in a fresh child process.