FED-3236 Docs: add more details around connect vs hooks

[greglittlefield-wf]

Motivation

The null safety migration guide could use a little more detail to help guide consumers on whether to migrate connect-ed components as is, vs first migrating them to use hooks.

Also, our Redux docs don't communicate a preference between connect or hooks, unlike the official React Redux docs which recommends hooks:

We recommend using the React-Redux hooks API as the default approach in your React components.

The existing connect API still works and will continue to be supported, but the hooks API is simpler and works better with TypeScript.

Changes

• Add info in migration guide around preferring hooks, and caveats to migrating them
• Update Redux docs to prefer hooks, and list hooks ahead of connect in TOC

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:
    • Formatting looks good and all links work in rendered markdown
  • 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

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

[aaronlademann-wf]

+1 / QA +1

@Workiva/release-management-pp

[rmconsole-wf]

+1 from RM