Finish the Pangular Inspector rename: package name, MCP name and leftover ng-devtools text #211

The package moves to the pangular-inspector npm org (https://www.npmjs.com/org/pangular-inspector). The package name is decided: @pangular-inspector/devtools (#212). Nothing has been published under the org yet.

To do before the first publish:

• Pick the final package name: @pangular-inspector/devtools.
• Set up the npm trusted publisher for the new name (see build(release): publish the package from a release workflow #190).

The CLI command is pangular.

Also left from #208:

• MCP server name in the setup samples (claude mcp add ng-devtools, "ng-devtools": {…} in mcp-server.md and kitchen-sink.md). Renaming it to pangular changes the tool names agents see (mcp__ng-devtools__… to mcp__pangular__…).

• The casual "ng-devtools" in user and agent facing text: live-route.ts and store-inspector.ts ("the dev server with ng-devtools"), popup.ts ("Mount the ng-devtools hub"), timeline-limits.ts ("the ng-devtools configuration"), vite.ts ("ng-devtools only answers requests from this machine", quoted in security.md and vite.md), hub.ts ("ng-devtools MCP token:", quoted in mcp-server.md), and the [ng-devtools] log prefix.

• Internal names, if we want them renamed too: ng-devtools:* RPC and tool names, __ng-devtools URLs, window.__ngDevtools* globals, NgDevtools* APIs, ng-devtools.config.json, NG_DEVTOOLS_* env vars, the packages/ng-devtools folder, the repo name and the docs URL (move to pangular-inspector.dev once it's live).

• The MCP server name agents see is ng-devtools (devframe). devframe builds it from the devframe id, so it changes when the id is renamed.

• Docs social card apps/docs/public/og.png still shows the old name and package.

• Add a README to packages/ng-devtools so the npm page isn't empty.