feat(driver-bench): add driver benchmarks to dbx-tools

[nbbeeken]

Description

What is changing?

• Pulled over the benchmarks from the driver, keeping git history
• Migrated to TS and mjs
• Fixed TS issues
• Added a small CLI script to make the benchmarks runnable.

Is there new documentation needed for these changes?

No

What is the motivation for this change?

I find myself comparing two copies of the driver a lot, with and without work-in-progress changes. Moving to a separate repo helps with making the benchmarks take a driver copy as an input. I would often make the change locally to accept a path as an ENV var but trample it when I needed to reset the driver to main.

Double check the following

• Ran npm run check:eslint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket