Remove the engine 0.6.2 conformance exceptions once both families peer 0.6.2

[wmadden-electric]

#313 ships @prisma/cli-engine 0.6.2. @prisma/composer-cli and @prisma/orm-toolchain still peer 0.6.1, so #313 adds two entries to exceptions in packages/cli/scripts/conformance.ts. They allow that mismatch until both packages release against 0.6.2. #280 and #291 handled the 0.6.1 transition the same way.

Steps

• fix(engine): print the CLI name instead of a literal {bin} in hints and messages #313 merges and engine 0.6.2 is published to npm.
• prisma/composer: pin engine 0.6.2 and release. The branch claude/engine-0.6.2 has the package.json changes; the lockfile waits for the publish.
• prisma/orm: pin engine 0.6.2 and release. The branch claude/engine-0.6.2 has the package.json changes; the lockfile waits for the publish.
• prisma-cli pins both releases (the update-product-versions workflow opens that pull request).
• Replace the two entries with exceptions: [], and check pnpm check:conformance on the release channel and with PUBLISH_CHANNEL=dev.

Why it matters

While the entries exist, the check allows a prisma that installs two engine copies. An entry left in place after the transition would let a real mismatch through the next time those versions meet.