[e2e] add support to report extra information

[CareF]

Description

Added an extra field extraInfo in lib/common.dart. Use case is to use the field to report performance. E.g. in flutter/flutter#61509, I'm migrating one existing test to an e2e based performance test. The use case is not complete because I still need to add other performance metrics but for a demo of the use case it's sufficient.

I'm not naming it to performance because in some of our device lab test the reported value is not for performance.

Related Issues

Resolves flutter/flutter#61490

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.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (flutter analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
• I updated CHANGELOG.md to add a description of the change.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.

[CareF]

It might be good to put some part of https://github.com/CareF/flutter/blob/e2e_trial/dev/benchmarks/macrobenchmarks/test/util.dart to E2E, but I'm not sure for that.

[dnfield]

Can you add some test(s) for this?

[CareF]

Can you add some test(s) for this?

@dnfield The test would require running on a device. I think I can add something to the example as test, though I don't think it will be tracked by CI.

[dnfield]

You should be able to write some unit tests right?

[CareF]

You should be able to write some unit tests right?

Currently we don't have any unit test for E2E, and I kind of believe it's because this package is all about adapting for running tests for different ways. But yeah it's probably the good point to start unit test here.

[CareF]

@dnfield Unit test done. I'm a little bit proud for coming up a way to unit test the binding.

[dnfield]

LGTM

[liyuqian]

LGTM with one nit.