fix: resync lockfile and miner's expected-engine.version for the v2.0.0 cut

release-please regenerated this branch from current main, which reintroduced
two issues already fixed once on the branch's prior incarnation:

- package-lock.json was missing an entry for @loopover/engine@1.0.0 (a
  dependent's still-published-range requirement), so npm ci rejected it as
  out of sync. Regenerated via npm install.
- packages/gittensory-miner/expected-engine.version still pinned 1.0.0, which
  scripts/check-engine-parity.ts's version-skew tripwire compares against the
  real packages/gittensory-engine/package.json (now 2.0.0) and fails on
  mismatch. Synced to 2.0.0, same as the prior cut.

Author: JSONbored

package-lock.json

@@ -1 +1 @@
-1.0.0
+2.0.0