fix: --max-backoff accepts seconds, not ms

[jrodewig]

Problem

The help text and tests for --max-backoff flag state/imply it accepts milliseconds.

The JS driver's corresponding maxBackoff client config option accepts values in seconds, not milliseconds. The value is converted from seconds to milliseconds here: https://github.com/fauna/fauna-js/blob/main/src/client.ts#L467-L468

Unless I missed it, the CLI does do any conversion of --max-backoff values so it should accept seconds.

Solution

Update the help text and tests to indicate --max-backoff accepts seconds.

Result

Accurate help and tests for the CLI.

Testing

npm run test:local is 🟢

[ptpaterson]

Yep! Thank you for catching!

[doom-weaver]

Yikes, we have some in seconds and some in milliseconds? We need to fix that in the driver(s) and make them all milliseconds.