Add validation to enable Save attributes and Save variations buttons

[octaedro]

All Submissions:

• Have you followed the WooCommerce Contributing guideline?
• Does your code follow the WordPress' coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

This PR disables the Save attributes and Save variations buttons until a value is added in the Name and Value fields.
We want to prevent triggering the action with empty values.

Closes #37021.

How to test the changes in this Pull Request:

• Have you followed the Writing high-quality testing instructions guide?

1. Go to Products > Add New > Product data > Attributes
2. The button Save attributes will be disabled.
3. Add a name and one or more values.
4. The save button should be enabled after filling out the inputs.
5. Next to Product data change the product type to Variable product.
6. Go to Variations and repeat steps 3 and 4.
7. The save buttons should work correctly.

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you created a changelog file for each project being changed, ie pnpm --filter=<project> changelog add?
• Have you included testing instructions?

FOR PR REVIEWER ONLY:

• I have reviewed that everything is sanitized/escaped appropriately for any SQL or XSS injection possibilities. I made sure Linting is not ignored or disabled.

[codecov]

Codecov Report

Merging #37046 (7475492) into trunk (6f8f35b) will increase coverage by 0.0%.
The diff coverage is 87.5%.

Additional details and impacted files

@@           Coverage Diff            @@
##             trunk   #37046   +/-   ##
========================================
  Coverage     46.7%    46.7%           
+ Complexity   17188    17187    -1     
========================================
  Files          429      429           
  Lines        64821    64829    +8     
========================================
+ Hits         30251    30276   +25     
+ Misses       34570    34553   -17     

Impacted Files	Coverage Δ
...ocommerce/includes/admin/class-wc-admin-assets.php	0.0% <0.0%> (ø)
plugins/woocommerce/includes/class-wc-tracker.php	89.8% <100.0%> (+0.1%)	⬆️
.../includes/import/class-wc-product-csv-importer.php	75.1% <100.0%> (+0.2%)	⬆️
...lugins/woocommerce/includes/wc-order-functions.php	76.4% <0.0%> (+0.1%)	⬆️
plugins/woocommerce/includes/class-wc-tax.php	79.0% <0.0%> (+0.5%)	⬆️
...udes/data-stores/class-wc-order-data-store-cpt.php	91.1% <0.0%> (+3.5%)	⬆️

[github-actions]

Test Results Summary

Commit SHA: 7475492

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	1m 10s
E2E Tests	189	0	0	6	0	195	13m 20s

---

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.

[octaedro]

I removed this validation in this commit because we're already disabling the button and it would duplicate the validation.
I'm not opposed to being more defensive, but I wanted a second opinion.

[octaedro]

We need to call this event because the Playwright method page.fill is not triggering the keyboard event. I we don't do this the e2e will fail.

[nathanss]

I found some bugs, the validation is not keeping track of all actions that can make it change. Some action seems to be making it lose "sync":

bug1.mov

bug2.mov

[octaedro]

Nice catch @nathanss!
I just fixed the bugs you found, could you take another look at this PR?

[nathanss]

Nice job. The issues seem to have been fixed! Approving it.

[jtobiesen]

zen- 6267640, experiencing bug 2 from @nathanss earlier video.