[flutter_tools] Separate style and data from AnalysisError

[figureConan]

Extract error data structure and wrap it with command line styles according to the platform, terminal, fileSystem.

Description

#49589 commit reduce context usage in analyze command and tests, and also introduce new variables(platform, terminal, fileSystem).These new variables affect output styles in different environments.
I suggest to extract error information data structure from the AnalysisError class. So we can use WrittenError for plain text content. And wrap WrittenError with AnalysisError.

Related Issues

Replace this paragraph with a list of issues related to this PR from our issue database. Indicate, which of these issues are resolved or fixed by this PR. There should be at least one issue listed here.

Tests

I added the following tests:

Reuse flutter analyze command test case.

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I signed the CLA.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I updated/added relevant documentation (doc comments with ///).
• All existing and new tests are passing.
• The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Did any tests fail when you ran them? Please read Handling breaking changes.

• No, no existing tests failed, so this is not a breaking change.
• Yes, this is a breaking change. If not, delete the remainder of this section.
  • I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
  • I got input from the developer relations team, specifically from: Replace with the names of who gave advice
  • I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

[fluttergithubbot]

This pull request was opened against a branch other than master. Since Flutter pull requests should not normally be opened against branches other than master, I have changed the base to master. If this was intended, you may modify the base back to dev. See the Release Process for information about how other branches get updated.

Reviewers: Use caution before merging pull requests to branches other than master, unless this is an intentional hotfix/cherrypick.

[fluttergithubbot]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

[fluttergithubbot]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

[jonahwilliams]

It would be nice to add some unit test coverage to WrittenError. The existing tests are mostly integration and don't really cover the small cases like JSON serialization well.

[figureConan]

It would be nice to add some unit test coverage to WrittenError. The existing tests are mostly integration and don't really cover the small cases like JSON serialization well.

Thank you williams for reviewing, all fixed.

[jonahwilliams]

LGTM

Except for the small change in the test

[jonahwilliams]

@IncludeCmath this will land automatically once the build is green, all good to go here 👍

[figureConan]

Google testing is pending @jonahwilliams