Add analytics wiring RPC functions

[mathemancer]

Fixes #4110

Adds:

• analytics.view_report, An RPC function to show an example usage report.
• analytics.initialize, An RPC function to turn on analytics reporting
• analytics.disable, An RPC function to disable analytics reporting
• mathesar.analytics.upload_initial_report, A Mathesar-layer function to handle one-time installation report (used by template)

There was already a function mathesar.analytics.initialize_analytics, A Mathesar-layer function to turn on usage statistics (used by template), so this didn't need implementing.

Technical details

For now, the analytics URLS are hardcoded in Prod mode, but aren't in dev mode at all. To add analytics wiring for dev mode, copy the production settings for MATHESAR_ANALYTICS_URL and MATHESAR_INIT_REPORT_URL to your .env file. This should only be used for testing analytics wiring. Avoid leaving those variables set in dev mode, since that will cause your dev setup to emit analytics reports to our actual collector infrastructure.

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the develop branch of the repository
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no
  visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[pavish]

The code & documentation is good for me to get started on the frontend.

[Anish9901]

LGTM!