Init logs and escape messages and refactor loggers

[armanddidierjean]

Add a new structure to use different LoggerOutput on the web and on mobile devices. PrintLoggerOutput can be used on the web to display logs in the console.

Closes #226
Closes #277

How to tests?

As we use two LoggerOutput, one on the web and one on mobile devices, the two platform should be tested.

On the web:

• open the browser console
• find an action that log something
• check a message DATE | LEVEL | MESSAGE was printed in the console

On iOS/Android:

• find an action that log something
• go to settings>log
• check that logs are readable

[maximeroucher]

Now I look like a clown for this one 😄

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 120 lines in your changes are missing coverage. Please review.

Project coverage is 54.71%. Comparing base (0d9fc27) to head (ccadf51).

Files	Patch %	Lines
lib/tools/repository/repository.dart	0.00%	38 Missing ⚠️
lib/tools/logs/file_logger_output.dart	0.00%	36 Missing ⚠️
lib/tools/repository/logo_repository.dart	0.00%	20 Missing ⚠️
lib/tools/logs/logger.dart	0.00%	19 Missing ⚠️
lib/tools/logs/print_logger_output.dart	0.00%	6 Missing ⚠️
lib/tools/logs/log.dart	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #353      +/-   ##
==========================================
- Coverage   54.78%   54.71%   -0.08%     
==========================================
  Files         166      168       +2     
  Lines        3665     3670       +5     
==========================================
  Hits         2008     2008              
- Misses       1657     1662       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[maximeroucher]

Nice one !

[guillaumetavernier]

It seems like there is a problem while parsing some logs

[armanddidierjean]

It seems like there is a problem while parsing some logs

We changed the way logs are stored in a file, thus the app will be unable to parse already existing logs.
We could add code to parse the old syntaxe, but I'm not sure it's worth doing:

• that would requires more work, and code, to support a syntax that is not used anymore
• these old logs were already broken. We won't be able to parse them correctly because messages can contains hyphens, which was the separator between the date, level and message.
• older logs are usually not relevant, and the content of the log is shown in the error