Enum + event constructors added for doctor events

[eliasyishak]

• Part of: ☂️ package:unified_analytics implementation in flutter tool flutter/flutter#128251

As part of the migration for flutter doctor events, this PR introduces the new enum and Event constructors for the doctor related events

Using this event, we can create a query to check how validator results change over time, sample query below

Additionally, with the doctorInvocationId being used to aggregate data across multiple doctor validators, we can get a percentage of validators that returned success in one invocation. (ie. there was 9 validators that returned success out of 10, so we can calculate 90% of successes for that invocation)

The above shows the average of all percent successes for a given week for all users.

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[christopherfujino]

Can you add a test where we construct an Event.doctorValidatorResult()? It might not be a ton of value, but at least it would catch the place where we add a required constructor parameter, which would be a breaking change.

[eliasyishak]

Can you add a test where we construct an Event.doctorValidatorResult()?

I think that's a great idea actually, I have captured this as a separate issue so that I can handle all of the constructors we have in event.dart... i guess the idea there would be if we remove (or add a non-optional) parameter, we would need to bump the major version for this package since that would be a breaking change?

EDIT: I have added the test for the new Event constructor in this PR actually, I will use the issue above to create tests for the other Event constructors though because I would like to use this PR as an example for how to create PRs for future events we add

[christopherfujino]

LGTM

[github-actions]

Package publishing

Package	Version	Status	Publish tag (post-merge)
package:unified_analytics	5.0.0	ready to publish	unified_analytics-v5.0.0
package:extension_discovery	2.0.1-wip	WIP (no publish necessary)
package:graphs	2.3.2-wip	WIP (no publish necessary)
package:cli_config	0.1.2	already published at pub.dev

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.