FEDX-1599: fixed validation publish condition

[matthewnitschke-wk]

FEDX-1599

Pre dart 3, running dart pub publish --dry-run would transitively execute dart analyze --fatal-infos under the assumption that all info lints should be resolved before publishing a dart package

There is an escape hatch --force where this check was ignored.

This was decided overkill, and just dart analyze is now run in dart. This change was applied in dart 3

Since we commonly index/publish dart 2 packages in gha-dart-oss, we have to support both approaches, and --fatal-infos is a stopgap for the action.

As a solution, we've decided to write custom validation steps for dart 2 for the criteria that we want to enforce (specifically the changelog update), and for dart 3, continue to use dart pub publish --dry-run

On the publish side of things, we need to --force publish for dart 2, but dart 3 should be able to publish without issue

[aviary-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.

[matthewnitschke-wk]

QA +1

• See test run on this release PR: RM-263537 Release dependency_validator 4.1.1 dependency_validator#129

[matthewnitschke-wk]

🚀 @Workiva/release-management-p 🚢

[rmconsole-wf]

+1 from RM