Wondering if there's some better flow to make (non-factory) developers more easily try and access factory stuff, especially when there are reports "test XXX failed".

Since the toolkits are pretty small, I wonder if we should simply embed install_factory_toolkit.run into somewhere in test image (say stateful:/cros_payloads, just like how factory_install installs it).

So when developers install a test image, he can do
 sh /mnt/stateful_partition/cros_payloads/install_factory_toolkit.run; reboot
To access factory UI.

Meanwhile I wonder if this can help removing /usr/local/factory-mini/{gooftool,factory.par}.

With this, maybe we can also revise the build artifacts on buildbot, say

 - factory_shim.zip contains factory_install (reset) shim only.
 - factory_toolkit.zip contains only the toolkit (installer).

Also, we may change the build config for '-factory' configs to build only factory_toolkit.zip.