Supersedes #67520.

It's still early days for the 7.0 cycle, so expect this tracking issue to be frequently edited in the next couple of days.

Enhancements

• Filter available source items for a given attribute by format.
  • See this preliminary exploration and discussion.
  • We'll do this in close collaboration with @oandregal, who's approaching formats for the Fields API. See the tracking issue and this example.
• Open up "Pattern Overrides" and therefore intern block bindings to custom dynamic blocks #64870
  • Related exploration: Pattern Overrides: Infer partial syncing supported blocks from the server #72391

Explorations

• Bind multiple attributes to a single source. Example: Bind Image block's url, alt, title attributes to post's featured image (exposed via core/post-data source).
  • Related exploration: Block Bindings: Try using __default for generic bindings #71002
• Try binding a block that requires a "repeater" concept. Example: Bind Gallery block to list of images.
• Streamline the API based on recurring usage patterns in getValues and getFieldsList.
  • Examples include passing more arguments to them (e.g. block name, attributes); or providing additional ways for a block source to communicate that it will not expose and source items for a given block, attribute, or other context. (Things that are currently done by e.g. returning [] from getFieldsList, based on certain criteria.)
• Block Bindings: Add support for the block visibility attribute #73461

Code Quality

• Block Bindings: Fix core/term-data source bug, refactor, add unit test coverage #73366
• Break packages/block-editor/src/hooks/block-hooks.js into individual components; move those into packages/block-editor/src/components/block-hooks/.
• Block Bindings: Remove 'Bindings' panel from e2e test plugin #72096