fix(pdi-scanner): use a smaller USB buffer in development

[eventualbuddha]

Overview

Closes #5541

Demo Video or Screenshot

❯ cargo run --example scan_forever --release
   Compiling pdi-scanner v0.1.0 (/media/parallels/WorkingFiles/code/vxsuite/libs/pdi-scanner)
    Finished `release` profile [optimized] target(s) in 1.53s
     Running `/media/parallels/WorkingFiles/code/vxsuite/target/release/examples/scan_forever`
waiting for sheet…
event: BeginScanEvent
event: EndScanEvent
Saved images from scan:
- Top: scan-0000-top.png
- Bottom: scan-0000-bottom.png
waiting for sheet…
^Creceived SIGINT
exiting

❯ NODE_ENV=production cargo run --example scan_forever --release
   Compiling pdi-scanner v0.1.0 (/media/parallels/WorkingFiles/code/vxsuite/libs/pdi-scanner)
    Finished `release` profile [optimized] target(s) in 3.28s
     Running `/media/parallels/WorkingFiles/code/vxsuite/target/release/examples/scan_forever`
Error: 
   0: failed to receive: timed out waiting on channel
   1: timed out waiting on channel

Location:
   libs/pdi-scanner/examples/scan_forever.rs:66

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Testing Plan

See above.

[arsalansufi]

LGTM!

[arsalansufi]

One thing I'm unsure about is whether we also need to consider whether this is a VxDev setup vs. true prod. On VxDev, NODE_ENV is production, but REACT_APP_VX_DEV is set to true so that we can distinguish it from true prod, e.g.

vxsuite/libs/auth/src/config.ts

Lines 24 to 26 in 0d0e272

	function shouldUseProdCerts(): boolean {
	return isNodeEnvProduction() && !isVxDev() && !isIntegrationTest();
	}

My quick sense is that, since VxDev isn't using VMs, it doesn't need the smaller buffer.

So all probably fine as is, just wanted to flag

[eventualbuddha]

Let's do the simpler version to start. If it turns out VxDev doesn't work, we can update it.

[arsalansufi]

Yup sounds right to me!