Remove configstore - fixing npm vulnerability

[herecydev]

Resolves https://www.npmjs.com/advisories/1213 and by extension gatsbyjs/gatsby#26128

I couldn't see any use of this package @davewasmer. Let me know if I'm incorrect.

[herecydev]

@davewasmer do you have any comments with this PR? It would be really good to remove the vulnerability from Gatsby (which is dependant on this change)

[hoobdeebla]

cc @zetlen

[JackHowa]

should I keep #64 open upgrading configstore or is removing it the priority? sorry to bother @zetlen @Js-Brecht

[herecydev]

The reason I opened this PR is because I'm pretty sure it's not used. So removing it would be preferable. If it turns out it is used then we can go with your PR.

[Js-Brecht]

I believe configstore was a part of the initial development effort, but its intended usage never made it to the remote
967e4c1

Looks like that import was stripped in January 2018:
e0ad2d6#diff-f41e9d04a45c83f3b6f6e630f10117feL12

I can't find its implementation in devcert-san, either. So according to the history, it only ever appeared as an import in index.ts... its intended purpose may be forever lost. I'm all for getting rid of it. Might as well get rid of @types/configstore, too.

[JackHowa]

thanks @Js-Brecht. I will close mine #64 then to reduce confusion @zetlen

[zetlen]

Thanks for your patience, folks. I'm reviewing this now; I think it's likely that configstore is no longer used, but I'll check.

[zetlen]

LGTM, thank you