FED-3476 Adjust builder for Dart 3

[robbecker-wf]

Summary

The over_react builder fails to generate code when there are analysis errors in the source file, regardless of their severity, due to the short-circuit here.

Historically, this hasn't been an issue since we do a non-resolved AST parse, and most infos/warnings require resolved AST.

However, apparently the warning for bad doc comment directives comes through in unresolved AST.

This causes failures to emit several over_react.g.dart files due to doc comments like this:

  /// Optional props to forward to the `ClickAwayListener` component
  /// when {@link disableClickAwayListener } is `false`.

and also outputs this warning:

[WARNING] over_react:overReactBuilder on package:unify_ui/src/components/custom/popper_trigger/popper_trigger.dart:
lib/src/components/custom/popper_trigger/popper_trigger.dart(2016..2019): Doc directive 'link' is unknown.

This issue should not prevent over_react from generating code.

[greglittlefield-wf]

• Changes look good
  • We can follow up to add regression tests and re-asses any dev experience improvements
• Verified behavior locally
  • In over_react examples, analysis warnings/errors no longer prevent over_react builder from attempting to generate code
  • Packages that previously couldn't build on Dart 3 due to analysis warnings can now build
  • No regressions when building one of our larger apps

+10

[greglittlefield-wf]

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM