INTL-1228: Attempt to reduce merge conflicts on _intl.dart files

[alanknight-wk]

Motivation

There are still too many merge conflicts on _intl.dart files.

Changes

• Automatically call 'dart_dev format' on the file. If that fails (most commonly because the repo is not set up for dart_dev) print an error message at the end.
• Put an extra line break between methods to make it less confusing for the merge algorithm.

Release Notes

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:

QA Checklist

• Tests were updated and provide good coverage of the changeset and other affected code
• Manual testing was performed if needed
  • Steps from PR author:
  • Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• A Frontend Frameworks Design member has reviewed these changes
• There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• For release PRs - Version metadata in Rosie comment is correct

[aviary2-wf]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[alanknight-wk]

QA +1 CI Passes, tried it out on graph_app

[alanknight-wk]

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM