feat(): Add Splitbee analytics for pass downloads

[luisivan]

PS: On a different note, we should add Prettifier config files to all projects to avoid noise in PRs

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
mobile-passport	✅ Ready (Inspect)	Visit Preview	Jul 1, 2022 at 2:01PM (UTC)

[aahna-ashina]

@luisivan This PR is both adding Splitbee and doing a lot of refactoring at the same time, so it's not easy for code reviewers to read the Splitbee code diff. Can you either 1) create one PR per change (one PR for refactoring, and another for Splitbee), or 2) create one PR with one commit per change (one commit for refactoring, and another for Splitbee)? Thanks! 😃

(Here is a great pull request philosophy: https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#pull-request-philosophy)

[luisivan]

Yeah... that's what I was mentioning above, since we didn't have a Prettifier config, just doing a save on my editor refactored the whole thing 😄

Maybe it's best to first merge #34, and then this one after (and then the changes will only affect Splitbee)

[luisivan]

@aahna-ashina ready to review again!

[aahna-ashina]

This looks good to me (though I have not tested the changes on localhost yet).

Out of curiosity: Where will the collected analytics be made available? On the Splitbee website I'm assuming?

[aahna-ashina]

@luisivan This PR will be closed when we merge #73 because we can get the same pass details by querying the downloads table that was added: 90afce2

select time_of_download, platform, address, passport_id from downloads;