Composite: accept store props on top level component

[ciampo]

What?

Extracted from #64723

Tweak Composite so that store props can be also passed to the top-level Composite component.

Why?

This is the first step towards removing explicit usage of the Composite store. All props that were previously passed to the useCompositeStore hook can be now passed to the top-level component instead.

This PR is the requirement for all upcoming refactors.

How?

By changing the type defs and reconciliating existing store objects.

Testing Instructions

Make sure that existing usages of Composite continue to work.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ciampo <mciampini@git.wordpress.org>
Co-authored-by: tyxla <tyxla@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Flaky tests detected in fb1db16.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/10644161549
📝 Reported issues:

• [Flaky Test] Users can dynamically customize the appender #42174 in /test/e2e/specs/editor/plugins/inner-blocks-render-appender.spec.js

[tyxla]

LGTM 👍

Tested in the inserter and in data views, all works well.

🚀

[tyxla]

Any good reason to prefer || to ?? here?

[ciampo]

Main reasons is that I copied the same style as the ariakit repo when dealing with store fallbacks:

https://github.com/ariakit/ariakit/blob/main/packages/ariakit-react-core/src/composite/composite.tsx#L145-L146

Also, store shouldn't have falsy values ('', 0) which would cause || to behave differently than ??