CPLAT-6376 Add helpful error message when @Component() is used with UiComponent2

[sydneyjodon-wk]

Motivation

Right now, accidentally using @Component() instead of @Component2() gives you an unhelpful error message.

require.js:143 Uncaught Error: UngeneratedError: `Symbol("typedPropsFactoryJs")` should be implemented by code generation.

Ensure that you're running a build via build_runner.
    at Object.dart.throw (dart_sdk.js:4604)
    at basic_with_state._$BasicComponent.new.typedPropsFactoryJs (component_base.ddc.js:550)
    at basic_with_state._$BasicComponent.new.newProps (component_base.ddc.js:388)
    at basic_with_state._$BasicComponent.new.getDefaultProps (abstract_inheritance.ddc.js:1973)
    at Object.react_client._registerComponent2 (react.ddc.js:864)
    at react_client._registerComponent (react.ddc.js:849)
    at Object.dart._checkAndCall (dart_sdk.js:4807)
    at Object.dart.dcall (dart_sdk.js:4812)
    at Object.src__component_declaration__component_base.registerComponent (component_base.ddc.js:3041)
    at get $BasicComponentFactory (abstract_inheritance.ddc.js:2132)
    at Object.desc.get [as $BasicComponentFactory] (dart_sdk.js:3639)
    at basic_with_state._$$BasicProps.new.get componentFactory [as componentFactory] (abstract_inheritance.ddc.js:2041)
    at basic_with_state._$$BasicProps.new.call (component_base.ddc.js:2746)
    at Object.index.main (abstract_inheritance.ddc.js:2632)

We need to provide a runtime error with a helpful message when this occurs.

Changes

• Add better messages to existing UngeneratedErrors for members that were added in UiComponent2.
  • typedPropsFactoryJs
  • UiComponent2 props getter
  • UiStatefulComponent2 state getter
• Write an integration test to check that a helpful error message is thrown when rendering a UiComponent2 with a @Component() annotation.

Release Notes

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:
@kealjones-wk @aaronlademann-wf @greglittlefield-wf @joebingham-wk

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 Client Platform 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.

[joebingham-wk]

This looks great to me - I didn't catch anything I'd do differently!

+1

[greglittlefield-wf]

+10

Nice job @sydneyjodon-wk!

@Workiva/release-management-p