refactor(create): drop "selected 'X' from @org/create" breadcrumb

Removed the `prompts.log.info('selected ... from ...')` line that used
to precede every manifest-driven template resolution. Rationale
(cpojer, PR #1398): the clack picker already prints the selected entry
above in its completed-prompt line, so the info note was a redundant
restatement of what the user just picked a moment before.

Impact on downstream failure context (the original reason the
breadcrumb was added, via the Cursor "chosen template fails to resolve
with context" finding): for the interactive path, the picker's own
completed-prompt line still shows the selection. For the
non-interactive `@org:name` path, the error surfaces from the
downstream runner — no vp-side framing. If that proves confusing in
practice, we can add the breadcrumb back only in failure paths.

Snap regenerated for `create-org-bundled` (the only fixture that
captured the line). 265 unit tests still pass.

Author: fengmk2

packages/cli/snap-tests/create-org-bundled/snap.txt

@@ -1,6 +1,4 @@
 > node $SNAP_CASES_DIR/.shared/mock-npm-registry.mjs -- vp create @your-org:demo --no-interactive --directory my-demo-app # bundled template: extract tarball, copy subdir
-
-selected 'demo' from @your-org/create
 ◇ Scaffolded my-demo-app
 • Node <semver>  pnpm <semver>
 → Next: cd my-demo-app && vp run

packages/cli/src/create/org-resolve.ts

@@ -86,10 +86,6 @@ async function resolveEntry(
   manifest: OrgManifest,
   entry: OrgTemplateEntry,
 ): Promise<OrgResolution> {
-  // Breadcrumb so a later downstream failure (e.g. the referenced
-  // `@org/template-web` package is missing) still tells the user what
-  // manifest entry produced that chain.
-  prompts.log.info(`selected '${entry.name}' from ${manifest.packageName}`);
   if (isRelativePath(entry.template)) {
     const extracted = await ensureOrgPackageExtracted(manifest);
     const bundledLocalPath = resolveBundledPath(extracted, entry.template);