✨ Async analytics

[arnavkulk]

Summary:

Make analytics run concurrently alongside cli commands

• Added package requests-futures (an extension of requests - what we use right now) for handling http requests asynchronously

New usage:

None, but the --use-analytics=True flag must be set for analytics to be recorded

Motivation:

CLI analytics are currently a blocking function on the actual command, and can take a long time to run for those with bad internet. This change sends analytics requests in the background, so that there is no blocking.

References (optional):

Closes #250

Test Plan:

For the following tests --use-analytics should be set to false

• Run any command (Expected output: command runs successfully, no output because analytics aren't running)

For the following --use-analytics should be set to true

• Run any command (Expected output: command runs successfully, analytics get sent. If there is an error with analytics, "Something went wrong while sending analytics!" is outputted)
• Run a command without an Internet connection (Expected output: analytics fails, the above message is outputted)

Testing Screenshots:

No Analytics:

Successful Analytics:

Failed Analytics:

[ayushuk]

Tested on my machine and lgtm just remove those old lines you commented out and we are good to merge

[ayushuk]

Out of scope for this pr but possibly might look into reading status codes for more specific error messages

[ayushuk]

lgtm