FED-2675 Only validate required props in null-safe components

[sydneyjodon-wk]

Motivation

over_react should only perform required prop validation for components that have migrated to null safety.

That way, during null safety migrations, packages that export prop mixins will be able to make props required without also causing them to be required in components that mix in those props in other packages (assuming those downstream components haven't migrated to null safety out of order), preventing a breaking change.

Then, when the components using the prop mixins are migrated to null safety, the required prop validation errors would take effect, at which point the consumers could add the appropriate @Props(disableRequiredPropValidation: {...}) annotations.

This will make it easier and safer to make props required in mixins that are used in wrapper components, like certain RMUI props mixins (like AutocompletePropsMixin).

See [this thread] for more info and an initial spike implementation: https://workiva.slack.com/archives/C063ZQ70Y7P/p1714608338493519

Changes

• Update runtime validation of required props to be a noop if a component isn't declared in a null-safe library (see spike impl linked above)
  • Add tests (non-null-safe props mixing in null-safe props mixin with required props)
• Update analyzer plugin to not warn for missing required props if the concrete props class is not declared in a null-safe library
  • Add tests
• Update required props markdown docs (added in FED-1885) to reflect this behavior

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
    • Verify added boilerplate tests fail without the change
    • Verify added analyzer plugin test files without this change
  • 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.

[greglittlefield-wf]

Changes and test coverage look great to me, +1!

[aaronlademann-wf]

+10

@Workiva/release-management-pp

[rmconsole-wf]

+1 from RM