Harden live assembly CLI e2e tests

[kvz]

Why

main CI for the SDK release went red in the live E2E job after @transloadit/node@4.10.8 was published. The package verify/build/unit/lockfile jobs all passed; the failing job was test/e2e/cli/assemblies-create.test.ts, and repeated runs failed on different live assembly-create cases.

A scheduled main run on a3b9b56 failed the same live suite earlier on June 18, before the tus rejection fix and release commits, so this is not caused by the SDK tus change.

What

• Adds the same one-retry policy to the live CLI assembly-create E2E suite that the live API E2E suite already uses.
• Moves the client-side single-assembly filesystem-stream assertion out of the live E2E suite and into the unit CLI assemblies test. The assertion now checks that filesystem inputs are passed as files and not eager uploads.

Verification

• corepack yarn workspace @transloadit/node test:unit --run ./test/unit/cli/assemblies-create.test.ts
• corepack yarn verify