chore: disentangle npm listing from the unrelated create-wp-plugin package

[akshat009]

Why

create-wp-plugin (no -cli) is a separate, unrelated npm package (by David Gwyer / wpgoplugins). Our metadata was helping it and misdescribing us.

Changes

README.md

• H1# create-wp-plugin → # create-wp-plugin-cli — matches the actual package name (the mismatch was just confusing; npm/GitHub render the H1 as the title).
• Add npm / CI / license badges under the H1.
• Remove the "the shorter create-wp-plugin name was already taken" blockquote — it was the last bare reference to the other package and framed ours as the runner-up.
• Section headings left untouched (no anchor-link breakage).

package.json

• description — dropped the stale v2 wording (SOLID/DI architecture (Container + Service Providers), removed in v3.0.0) → static bootloader with a Services locator, …, matching the current architecture (src/Services.php is literally a "Static service locator"; src/Plugin.php says "Not a service container").
• bin — removed the create-wp-plugin alias. Installing this no longer drops a create-wp-plugin executable on PATH that shadows the unrelated package. create-wp-plugin-cli is the sole bin; npm create wp-plugin-cli / npx create-wp-plugin-cli unaffected. package-lock.json already only listed the -cli bin, so no lockfile change.
• keywords — added wordpress-plugin, wp-cli, gutenberg, phpunit.

BACKLOG.md

• Closed NEW-56 ("add create-wp-plugin bin alias") as rejected — it directly contradicts the disentangling intent.

Done separately (live repo metadata, not in this diff)

• GitHub About description refreshed.
• GitHub topics rebuilt (18): dropped nodejs / scaffold / generator / php; added scaffolding, boilerplate-generator, npm-package, wordpress-vip, playwright, php82, wp-env, dev-tooling.

Verification

• npm test → 70/70 pass
• git diff touches exactly these 3 files