feat: initial plausible setup

[limwa]

Closes #1031.

This pull requests adds analytics collection to uni.

As of now, pageviews are collected using flutter_plausible's PlausibleNavigatorObserver, which automatically tracks which routes are being viewed. Clicks and other events will be collected as well, but I am still figuring out what is the best way to go about it.

Review checklist

• Terms and conditions reflect the current change
• Contains enough appropriate tests
• If aimed at production, writes a new summary in whatsnew/whatsnew-pt-PT
• Properly adds an entry in changelog.md with the change
• If PR includes UI updates/additions, its description has screenshots
• Behavior is as expected
• Clean, well-structured code

[limwa]

I still need to add widget click detection, but it has proven harder than I initially though, especially since dart:mirrors is not available in Flutter. As such, I'll have to use code generation (something I am completely unfamiliar with) to mark uni's widgets, so that, later on, I know which ones should be sent in the analytics event. Therefore, I suggest we split this PR into two different PRs: one for pageviews (this one) and another for click detection.

Regarding this PR, the terms and conditions still need to be updated and battery level / connectivity detection still need to be added.

[limwa]

Also, any clues on how to fix the linting error? @bdmendes @LuisDuarte1

[bdmendes]

@limwa:

• I'm not really sure what is causing the linting error, since the env file never existed on the repository and it never caused an error.
• I agree with splitting the PRs, but we should tackle the T&C here since this will deployed immediately to the beta track
• Also, about the code generation build steps, see i18n migration #475 for an example

[limwa]

• I'm not really sure what is causing the linting error, since the env file never existed on the repository and it never caused an error.

The linting error is being caused because I added the env file to the pubspec.yml, since I need it to be shipped with the app. It never caused an error because it was never added to the application bundle since the linting configurations changed.

• I agree with splitting the PRs, but we should tackle the T&C here since this will deployed immediately to the beta track

I agree. Who is going to handle this? If this is too sensitive to be discussed in public, you can DM me.

[bdmendes]

@limwa

• Aren't we using a new package that moved the env out of the assets? Just recalling it now
• Let's discuss that in-person

[limwa]

Huuu, I'm not sure, are we?

Update: I don't think we are, the GitHub Actions don't touch any .env file.

Update 2: We are using flutter_dotenv (https://pub.dev/packages/flutter_dotenv). You are still required to add the .env file to your assets.

[codecov]

Codecov Report

Merging #1038 (51d41b9) into develop (66fcc86) will decrease coverage by 0%.
Report is 2 commits behind head on develop.
The diff coverage is 0%.

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #1038   +/-   ##
=======================================
- Coverage       17%     16%   -0%     
=======================================
  Files          212     213    +1     
  Lines         6472    6535   +63     
=======================================
  Hits          1044    1044           
- Misses        5428    5491   +63     

[LuisDuarte1]

🚀 Good work!