token: use figgy-config to make sure extra opts are there

[zkat]

This fixes a reversion reported by @evilpacket and co, where we weren't sending some metadata and auth info on npm token ls. This has to do with the npm@6.6.0 rework.

[aeschright]

⭐️

[alexsasharegan]

Will this also resolve what looks like the same issue with the token subcommand? This output immediately follows a successful login. Of note, I do use TOTP 2FA.

$ npm token create --read-only
npm password: 
npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR!     npm login

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

/home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli   '/usr/bin/npm',
1 verbose cli   'token',
1 verbose cli   'create',
1 verbose cli   '--read-only' ]
2 info using npm@6.7.0
3 info using node@v10.15.1
4 verbose config Skipping project config: /home/alex/.npmrc. (matches userconfig)
5 info token creating
6 verbose stack Error: Unable to authenticate, need: Basic, Bearer
6 verbose stack     at res.buffer.catch.then.body (/home/alex/.npm-global/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
6 verbose stack     at process._tickCallback (internal/process/next_tick.js:68:7)
7 verbose statusCode 401
8 verbose cwd /home/alex/github.com/pictalk/pictalk
9 verbose Linux 4.18.0-13-generic
10 verbose argv "/usr/bin/node" "/usr/bin/npm" "token" "create" "--read-only"
11 verbose node v10.15.1
12 verbose npm  v6.7.0
13 error code E401
14 error Unable to authenticate, your authentication token seems to be invalid.
15 error To correct this please trying logging in again with:
15 error     npm login
16 verbose exit [ 1, true ]