Opt-In Telemetry, Security Patching and Environment Dumps

Is your feature request related to a problem? Please describe.
Allowing users to opt-in to telemetric submission will help the core team figure out how tauri is being used in devland. Making the approach public will help devland know how their users are getting on with Tauri apps.

Describe the solution you'd like
I think there is a good start here:
https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-telemetry/src/index.js
Combined with antivuln, it would be an excellent way for us to provide an additional service layer for those who want us to manage their security. Before you laugh and say I would never do that, just stop and think for a moment about how much work it is to stay on top of dependencies in today's development environment.

Additional context
I think in combination with #57 and our internal discussions about providing some kind of tauri interface like:

$ tauri audit

Which would dump everything known about the system - then I think we'd have a nice robust turn-key system that provides elegant solutions to helping developers stay safe in the semi-hostile environment of thousands of node modules and hundreds of crates and a variety of runtimes.

Start by reviewing the Gatsby telemetry implementation linked in the issue and the related discussion in #57. The proposal needs its scope and privacy model defined before implementation: opt-in telemetry, security patching, and the information reported by a possible tauri audit command should each have clear requirements and acceptance criteria.