[Experimental] Utilize WP generated class names to style interactivity stock filter block.

[samueljseay]

Changes proposed in this Pull Request:

@dinhtungdu and I agreed that we don't need to create our own unique class names or use bem style syntax, its overly verbose and doesn't add anything.

Instead we scope all styles to the class name generated for the block by WP, and also remove the BEM style prefix from any scoped class names. (To keep PR's small and testable I'm addressing one block at a time.)

Additionally, I noticed a lot of copy pasted styles from the old block that we don't use or need.

This is part of #43167

How to test the changes in this Pull Request:

1. Much like in [Experimental] Utilize WP generated class names when styling new active filters block. #44069, edit the product catalog or a page and alongside product collection add stock status filter.
2. Also in editor try different modes like dropdown/multiple etc
3. Check that styling looks good in editor and frontend.

Changelog entry

• Automatically create a changelog entry from the details below.

Significance

• Patch
• Minor
• Major

Type

• Fix - Fixes an existing bug
• Add - Adds functionality
• Update - Update existing functionality
• Dev - Development related task
• Tweak - A minor adjustment to the codebase
• Performance - Address performance issues
• Enhancement - Improvement to existing functionality

Message

[Experimental] Unify class naming in new interactivity stock filter block.

Comment

[github-actions]

Test Results Summary

Commit SHA: cad2980

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	0m 37s
E2E Tests	271	0	0	25	0	296	6m 29s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[dinhtungdu]

Another great simplification! Tested on JN and the stock filter block works well as before.

Note that the difference between the count data is expected because we're using StoreAPI in the editor. We may want to remove it to replace with preview data later.