feat: add more Woo conditions to Block Conditions module

[HardeepAsrani]

Closes https://github.com/Codeinwp/otter-internals/issues/198.

Summary

This PR adds:

• Product Category
• Product Tag
• Product Attribute

conditions to Block Conditions module.

Screenshots

---

Test instructions

• You can import WooCommerce's sample data to get a good set of products.
• Confirm all the conditions work when the taxonomy is present/absent.
• There are no debugging errors.
• This is made for Product Page, so you must be using a FSE theme for being able to customize the Single Product Template.

---

Checklist before the final review

• Included E2E or unit tests for the changes in this PR.
• Visual elements are not affected by independent changes.
• It is at least compatible with the minimum WordPress version.
• It loads additional script in frontend only if it is required.
• Does not impact the Core Web Vitals.
• In case of deprecation, old blocks are safely migrated.
• It is usable in Widgets and FSE.
• Copy/Paste is working if the attributes are modified.
• PR is following the best practices

[pirate-bot]

Plugin build for 698f507 is ready 🛎️!

• Download Otter – Page Builder Blocks & Extensions for Gutenberg - Production ~ Development
• Download Otter Pro - Production ~ Development
• Download Blocks Animation - Production ~ Development
• Download Blocks CSS - Production ~ Development
• Download Blocks Export Import - Production ~ Development

[pirate-bot]

Bundle Size Diff

Package	Old Size	New Size	Diff
Animations	263.48 KB	263.48 KB	0 B (0.00%)
Blocks	1.52 MB	1.52 MB	1.37 KB (0.09%)
CSS	92.73 KB	92.73 KB	0 B (0.00%)
Dashboard	195.5 KB	195.5 KB	0 B (0.00%)
Onboarding	153.14 KB	153.14 KB	0 B (0.00%)
Export Import	90.21 KB	90.21 KB	0 B (0.00%)
Pro	361.57 KB	364.44 KB	2.87 KB (0.79%)

[pirate-bot]

E2E Tests

Playwright Test Status:

Performance Results

serverResponse: 238, firstPaint: 165.75, domContentLoaded: 1568.3, loaded: 1569, firstContentfulPaint: 3476.4, firstBlock: 6714, type: 13.14, minType: 10.79, maxType: 18.52, typeContainer: 8.53, minTypeContainer: 8.19, maxTypeContainer: 9.34, focus: 34.41, minFocus: 27.74, maxFocus: 43.95, inserterOpen: 23.99, minInserterOpen: 21.34, maxInserterOpen: 37, inserterSearch: 0.75, minInserterSearch: 0.62, maxInserterSearch: 0.93, inserterHover: 3.41, minInserterHover: 2.82, maxInserterHover: 4.63, listViewOpen: 149.76, minListViewOpen: 131.75, maxListViewOpen: 170.55

[carlalexander]

Quick final note on the review as well related to commit history. I'll be doing a review of the commit history once the code changes are done. That said, I'll note for now that the chore commits should be merged into the feature commit. You don't have to fix that now if you want. I can do a review of the commit history at the end so you can just do all that then.

[carlalexander]

This is great @HardeepAsrani! Your refactor of the condition code was excellent! We're almost there.

Just to help show a bit what I'm thinking with the commit history, I would have made the refactor commit just the changes to the conditions. The rest I would have left as another commit that we're going to merge back into the feat commit.

[HardeepAsrani]

Thanks @carlalexander for the review. I wanted to ask about how you feel is the best way to manage commits here. Personally, I try not to alter commits to protect their integrity even if, at times, it makes history look a bit ugly.

But what would you suggest here? We squash all of them together or some other way?

[carlalexander]

@HardeepAsrani left you a message in slack. Let's try to find a time to connect and I can go over that with you. 🙂

[carlalexander]

@HardeepAsrani I ended up doing the rebasing because there were merge conflicts to resolve. If you'd have preferred to do it, let me know.

I also left a video in Slack about the refactor commit and what I would have liked to see in it. But otherwise, amazing work. Thank you! 🥳

[pirate-bot]

🎉 This PR is included in version 3.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀