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. fix(deps): build composer-cli against @prisma/cli-engine 0.6.2, the engine the next prisma CLI ships composer#325 is merged; no release contains it yet (latest is 0.25.0, which peers 0.6.1).
• prisma/orm: pin engine 0.6.2 and release. Done in fix(deps): build orm-toolchain against @prisma/cli-engine 0.6.2, which prints the CLI name where hints showed {bin} orm#30503, released as 8.0.0-rc.14.
• prisma-cli pins both releases (the update-product-versions workflow opens that pull request). The ORM pin is done in Follow the products' released versions: @prisma/orm-toolchain 8.0.0-rc.13 -> 8.0.0-rc.14 #327; the Composer pin waits on the release.
• Replace the two entries with exceptions: []. chore(cli): remove the orm-toolchain engine 0.6.2 conformance exception #328 removes the ORM entry; the Composer entry remains. Original step: 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.