flutter analyze --write breakes the parsing

[japawl]

flutter analyze takes --write=path/report-name.txt option argument. Reports generated in this way are slightly different than the flutter analyze, making flutter_lint unable to parse the results:

$ flutter analyze --no-fatal-infos --no-fatal-warnings > flutter_analyze_report.txt
1 issue found. (ran in 12.0s)
$ cat flutter_analyze_report.txt
Analyzing rtyst_flutter...                                      
   info • Sort constructor declarations before other members • lib/main.dart:23:3 • sort_constructors_first

$ flutter analyze --no-fatal-infos --no-fatal-warnings --write=flutter_analyze_report.txt
Analyzing rtyst_flutter...                                      
   info • Sort constructor declarations before other members • lib/main.dart:23:3 • sort_constructors_first
1 issue found. (ran in 13.2s)
$ cat flutter_analyze_report.txt
[info] Sort constructor declarations before other members (/builds/rtyst/rtyst_flutter/lib/main.dart:23:3)

Because --write is the supported way for flutter to generate reports, flutter_lint should work with it.