chore: bump @adobe/aio-cli-plugin-app-templates to 2.1.3 (APPBLD-5119) - #844

Patch-only dependency bump: pins package-lock.json's resolved @adobe/aio-cli-plugin-app-templates entry to 2.1.3 (declared range ^2 unchanged).

Why

Fixes ESM template loading in templates:install (JIRA APPBLD-5119, adobe/aio-cli-plugin-app-templates#83) — require() failed with "constructor is not a constructor" for ESM-packaged templates (e.g. dx/excshell/1, dx/asset-compute/worker/1 when built as ESM). #83 switches to dynamic import() with a .default unwrap, handling both ERR_REQUIRE_ESM and ERR_REQUIRE_ASYNC_MODULE.

aio-cli ships its own package-lock.json in the published npm package (see files in package.json), so a global npm install -g @adobe/aio-cli resolves dependencies from that committed lockfile rather than re-resolving ^2 fresh from the registry — a leaf release alone does not reach end users without this bump + a new aio-cli release.

Validated

• @adobe/[email protected] and 2.1.1 (previously locked version) have identical declared dependencies — this is a version/resolved/integrity-only lockfile change, no dependency-tree churn.
• npm test (jest + lint): 53/53 tests pass, 100% coverage, lint clean.
• npm run check-overrides: no override changes needed.
• Verified the new tarball installs and loads correctly (require('@adobe/aio-cli-plugin-app-templates/package.json').version === '2.1.3').