FED-2554 Companion codemods should not run on null-safe files

[sydneyjodon-wk]

Motivation

During null safety migrations, some repos will be incrementally migrated, and there's a good chance the over_react null safety companion set of codemods (the one that inserts nullability hints) will get run on a mixture of not-yet-migrated and already-migrated code.

To avoid adding a bunch of nullability hints to files that have already been migrated to null safety, which would have to be manually removed, we should update our codemods to not run on files that are already null-safe.

Changes

• Add short circuit to all companion codemod suggestors if the file is already null safe
• Add tests

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:
    • CI passes
  • 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.

[greglittlefield-wf]

+10, though I just realized we should also do the same for the required props codemod 😬

We can do that as a follow-up PR, though

[greglittlefield-wf]

+10

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM