Add OTP support for publish

[Joe Fleming]

When publishing packages using oao, if you have OTP enabled on the registry, the publish command will fail.

...snip...
2019-09-27T21:01:47.802Z                  npm ERROR | npm ERR! code EOTP
2019-09-27T21:01:47.803Z                  npm ERROR | npm ERR! This operation requires a one-time password from your authenticator.
2019-09-27T21:01:47.803Z                  npm ERROR | npm ERR! You can provide a one-time password by passing --otp=<code> to the command you ran.
2019-09-27T21:01:47.805Z                  npm ERROR | npm ERR! If you already provided a one-time password then it is likely that you either typoed
2019-09-27T21:01:47.806Z                  npm ERROR | npm ERR! it, or it timed out. Please try again.
2019-09-27T21:01:47.814Z                  npm ERROR | npm ERR! A complete log of this run can be found in:
2019-09-27T21:01:47.814Z                  npm ERROR | npm ERR!     /Users/username/.npm/_logs/2019-09-27T21_01_47_804Z-debug.log
2019-09-27T21:01:47.821Z                  npm INFO  |
2019-09-27T21:01:47.822Z                 main ERROR Command 'npm publish' failed [1] at packages/pkg1
...snip...

Everything else works, so you can jump into each of the packages and run publish manually, but that's not ideal.

It would be great if oao could instead prompt for the OTP code.

it would be acceptable if it supported the --otp argument like the npm command does.