chore: remove deprecated commands and clean up dead code for v1.0.0

[revanth0212]

Summary

• Removed the deprecated commerce init command and all init-only utilities (initialization.js, github.js, content.js, preview.js, openBrowser.js, mesh.js, configs.js, importer.js, mdast/, fetchWithRetry.js, sleep.js)
• Removed the commerce dev command and placeholder commerce test command
• Removed unused exports: selectOrganization from devConsole.js, readEnvFile/writeEnvFile from envFile.js
• Removed jsdom dependency (only used by deleted init utilities)
• Cleaned up README: removed init/dev command docs, Mesh Prerequisites, gh CLI prerequisite, init-specific troubleshooting, API Mesh references, and Templates section
• Updated CHANGELOG with a new 1.0.0 entry documenting all removals

21 files changed — 20,113 lines removed

After this PR, the plugin's commands are:

• aio commerce extensibility app-setup
• aio commerce extensibility tools-setup

Test plan

• Verify aio commerce extensibility app-setup still works correctly
• Verify aio commerce extensibility tools-setup still works correctly
• Confirm aio commerce init, aio commerce dev, and aio commerce test are no longer available
• Run npm test to ensure no broken imports or references

[rojoangel]

The tests are broken:
test/commands/commerce/hello.test.js imports ../../../src/commands/commerce/hello

aio-cli-plugin-commerce/test/commands/commerce/hello.test.js

Line 12 in 43221fc

import { HelloCommand } from '../../../src/commands/commerce/hello'

but the hello command no longer exists (it was part of the removed boilerplate). The test suite fails with "Cannot find module '../../../src/commands/commerce/hello'".

Please either remove this test file as part of the dead-code cleanup, or restore a minimal hello command if it’s still desired.

❯ npm test

> @adobe/aio-cli-plugin-commerce@1.0.0 test
> node --experimental-vm-modules node_modules/jest/bin/jest.js --testRegex '.+\.test\.js' --ci

(node:20594) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
 PASS  test/commands/commerce/index.test.js
 FAIL  test/commands/commerce/hello.test.js
  ● Test suite failed to run

    Cannot find module '../../../src/commands/commerce/hello' from 'test/commands/commerce/hello.test.js'

      at Resolver._throwModNotFoundError (node_modules/jest-resolve/build/resolver.js:427:11)

-|---------|----------|---------|---------|-------------------
 | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
-|---------|----------|---------|---------|-------------------
 |     100 |      100 |     100 |     100 |                   
  |     100 |      100 |     100 |     100 |                   
-|---------|----------|---------|---------|-------------------
Test Suites: 1 failed, 1 passed, 2 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        0.266 s, estimated 1 s

[rojoangel]

Update index command description

aio-cli-plugin-commerce/src/commands/commerce/index.js

Line 21 in 43221fc

IndexCommand.description = 'Spin up an Adobe Commerce Storefront on EDS using this CLI tool'

The description "Spin up an Adobe Commerce Storefront on EDS using this CLI tool" is from the old init-based workflow. Now that the plugin only exposes extensibility app-setup and extensibility tools-setup, consider updating to something like: "Commerce Extensibility commands for the Adobe I/O CLI" (or similar) so it matches the current scope.

[rojoangel]

Looks good to me, with some comments

[rojoangel]

Minor: The compare link for 1.0.0 points to .../compare/1.0.0...HEAD. Once this PR is merged, that’s correct. If you version from a tag (e.g. v1.0.0), you might use v1.0.0 in the link for consistency with other entries. Only if your release process uses a v prefix.