INTL-1591: Handle non-arrow intl functions

[alanknight-wk]

Motivation

The intl_suggestors are hard-coded to expect arrow functions, and crash with a parse error if you add one by hand and then try to run the codemod. This is sub-optimal. And pretty easy to fix. One place assumes you can split a string on the '=>' substring, and another place assumes AST structure, but can be easily adapted.

This is analogous to INTL-1589

Changes

Fixes, as above.

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

[aviary3-wk]

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]

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM