Don't override ref property when not configured to.

[PSpSynedra]

The current behavior of connect is to always pass along a ref property, event when the option forwardRef was not truthy or preset.

This pull request

• corrects this error by only forwarding a ref property when actually configured to.
• avoids problems, when accessing the forwarded but always undefined ref.
• fixes External property ref is always overridden with value undefined #2251

The error in the following use case is also fixed with this pull-request:

import WrappedComponent from '...'
function HocComponent(props) {
   const [wrapperRef, setRef] = useState(null)
   // The current behavior of connect would override the ref!
   return <WrappedComponent ref={setRef} {...props} />
}
export default connect(...)(HocComponent)

NOTE:
My initial intend was to remove the use of React.forwardRef(...) completely, but this would have broken the compatibility with React prior to version 19.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[PSpSynedra]

Unfortunately I cannot get the "Test Published Artifact expo (pull_request)" to pass.
When I run yarn install with node-22.18.0 as suggested by some internet search results, my local yarn.lock does not get changed.

Can I run the failing test locally on my machine to fix the issue?
Any suggestions on how to fix this?

[netlify]

✅ Deploy Preview for react-redux-docs ready!

Name	Link
🔨 Latest commit	27fd687
🔍 Latest deploy log	https://app.netlify.com/projects/react-redux-docs/deploys/68c7ade9c0648e000833e342
😎 Deploy Preview	https://deploy-preview-2252--react-redux-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.