✨Add Analytics

[BennyBot]

Summary:

Moves the recently added --no-sentry flag to default options.

Adds event tracking to google analytics for numerous CLI commands (commands listed below).
make, make-upload, make-upload-terminal, build-compile-commands, create-template, purge-template, fetch-template, apply-template, install-template, uninstall-template, query-templates, upgrade-project, new-project, info-project, upgrade, terminal, upload, ls-usb, upload-terminal, user-script, status, ls-files, read-file, write-file, rm-file, cat-metadata, rm-all, run

Adds --use-analytics BOOLEAN option to enable/disable analytics. Analytics are enabled by default.
Usage:
pros --use-analytics=False to disabled analytics
pros --use-analytics=True to enable analytics

Adds --no-analytics flag to default options to not send analytics for that event.
Usage:
pros <command> --no-analytics will not send analytics for this event.

Motivation:

Let us know where PROS is being used, what commands are called often, and the size of our userbase
Analytics go brrrr

References (optional):

Closes #121

Test Plan:

• uid generated and saved on first command use
• Events being sent and received by GA
• pros --use-analytics=False stops sending analytics
• pros --use-analytics=True starts analytics again
• pros <command> --no-analytics doesn't send analytics for that event
• Test default options --no-sentry flag

[kunwarsahni01]

Change from storing uid in json file to store in cli.pros file.

[BennyBot]

Change from storing uid in json file to store in cli.pros file.

Just finished that up, and appears to be working. Does cli.pros generate when the pros executable is run (pretty much does it still exist with vscode one-click)?