Make BATS work with npm dev setup on Windows

[jandubois]

To speed up dev cycles we want to make bats work with npm run dev.

• Introduce RD_USE_NPM variable to control this.

• Set the resources path to ../resources/... to locate rdctl and other bundled utilities.

• Modify factory_reset to stop the app first before running rdctl factory-reset.

• Use (cd ..; npm run dev) instead of rdctl start. Figure out how to pass parameters.

[mook-as]

Generally speaking, there's three or four places we would look for the RD install:

• System-wide installation (/opt, /Applications, C:\Program Files, depending on OS)
• User-wide install (Windows only, ~/AppData/Local)
• Locally built (dist/*-unpacked)
• We're adding unbuilt (npm run dev).

It might be good to have the environment variable cover picking a particular one out of those cases.

P.S. npm run dev -- --set foo.bar=true should work fine.

[jandubois]

Generally speaking, there's three or four places we would look for the RD install:

• System-wide installation (/opt, /Applications, C:\Program Files, depending on OS)
• User-wide install (Windows only, ~/AppData/Local)

Also on macOS at ~/Applications.

• Locally built (dist/*-unpacked)
• We're adding unbuilt (npm run dev).

It might be good to have the environment variable cover picking a particular one out of those cases.

I've implemented the basic mechanism in #4573, but further work is needed to make support for npm run dev more robust on macOS/Linux (shutdown/factory-reset), or implement it at all on Windows.

P.S. npm run dev -- --set foo.bar=true should work fine.

It does, but takes different form of parameters than rdctl start (see #4569). It is not possible to recreate the API name of the parameter from the rdctl version (because acronyms), so we should generate a translation function from the schema.

[jandubois]

This is working completely on macOS (and should work the same way on Linux), but the shutdown / factory-reset logic still needs to be implemented for Windows.