Price Filter: Introduce view block

[dinhtungdu]

What

• This PR closes two issue as the same time (#11306 and New Price Filter block powered by Interactivity API #10813) because the Price Filter block was used for experimenting new block structure.
• This PR introduces a new term called view block. This isn't a Gutenberg or WooCommerce term. With the block structure introduced in this PR, filter blocks don't need to fetch and process the data from Store API themselves, instead they just need to consume the data passed through context, that's why I called them view blocks. See Block structure for extensibility woocommerce#42178 for more detail.
• Move the logic calculating and enqueuing Interactivity Store to the Collection Filters block.
• The store data is passed to inner filter blocks through a context named filterData.
• Inner filter blocks (the Collection Price Filter in this case) consume that context to build the view. 
• View blocks must declare an attribute named filterType with a default value set to one of these strings to indicate their type: price, attribute , stock , or rating. Collection Filters block uses this attribute to build the filter data.
• View blocks can have their own data:
  • State: rangeStyle  in this case.
  • Attributes: showInputFields, inlineInput.

Fixes woocommerce/woocommerce#42178 #10813

Why

By delegating the data fetching and processing to the Collection Filters block, we

• simplify the filter block code and logic.
• reducing the duplication between filter blocks.

Testing Instructions

Please consider any edge cases this change may have, and also other areas of the product this may impact.

1. Add Product Collection > Collection Filters > Collection Price Filters to a new page.
2. See the block work in the editor preview and on the front end.

• Do not include in the Testing Notes
• Should be tested by the development team exclusively.

WooCommerce Visibility

Required:

• WooCommerce Core
• Feature plugin
• Experimental
• N/A

Checklist

Required:

• This PR has either a[type] label or a [skip-changelog] label.
• This PR is assigned to a milestone.

Conditional:

• This PR has a changelog description (if[skip-changelog] label is not present).
• This PR adds/removes a feature flag & I've updatedthis doc.
• This PR adds/removes an experimental interfaces, and I've updatedthis doc.
• This PR has been accessibility tested.
• This PR has had any necessary documentation added/updated.

Changelog

N/a

[dinhtungdu]

Closing in favor of woocommerce/woocommerce#42178