Stats updater fixes

[emerick]

Fix brave/brave-browser#3895

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Windows
  • macOS
  • Linux
• Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests && npm run test-security) on
  • Windows
  • macOS
  • Linux
• Verified that all lint errors/warnings are resolved (npm run lint)
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone

Test Plan:

• Start with a clean profile
• Launch Brave and keep it running for duration of test
• Verify that daily ping is sent on startup and looks accurate
• Wait 6 minutes (pings are checked every 5 minutes, so this factors in a little wiggle room)
• Set computer's clock ahead to the next day (or you could run this test at 11:55pm or so)
• Verify that daily ping is sent for this "new" day and that it looks accurate

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source