Fix "Translation loading for the woocommerce-square domain was triggered too early" error on WP 6.7

[iamdharmesh]

All Submissions:

• Does your code follow the WooCommerce Sniffs variant of WordPress coding standards?
• Have you written new tests for your changes, as applicable?
• Have you successfully run tests with your changes locally?
• Will this change require new documentation or changes to existing documentation?

---

Changes proposed in this Pull Request:

In WordPress 6.7, they changed the way translations are loaded which affects how and when translation strings should be triggered. With this change, any __() code called before the after_setup_theme is considered "too early" and will need to be updated to happen on a later hook. This PR updates code to fix these too-early translation notices.

Closes #258

Steps to test the changes in this Pull Request:

1. Ensure define( 'WP_DEBUG', true ); is set in wp-config.php.
2. Update to the latest version of WordPress 6.7.
3. Navigate to your Edit User Profile page and update the language to something other than "English."
4. Ensure there are no notices on the WordPress admin screen.

Changelog entry

Fix - Resolved "translation loading was triggered too early" issue in WordPress 6.7.

[dkotter]

This can go to UAT once QA passes

[qasumitbagthariya]

@iamdharmesh

Regarding the translation, there are no errors, but I noticed a deprecated error. Can you please check on your end? Is this related to this PR?

[qasumitbagthariya]

QA Update: ✅

As discussed with @iamdharmesh, this is not related to this PR and is not blocking it. Therefore, I am approving this PR and create a separate issue.