Added Version to WooCommerce 6.5's composer.json

[ObliviousHarmony]

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:

By default, Composer pulls the version of the current code from the branch name. In our case, since it has no idea what to call them, they are versioned as 1.0.0.0. When we run Core alongside the feature plugin, all of the PHP files included in it have a higher version. Our solution here is to add an explicit version to composer.json in order to tell Composer what to put instead of 1.0.0.0. The end result should be that Core's PHP class files are preferred and everything loads correctly.

Closes #32732.

How to test the changes in this Pull Request:

1. Run composer install in plugins/woocommerce.
2. Review plugins/woocommerce/vendor/composer/jetpack_autoload_classmap.php and verify that Core PHP files are 6.5.0.0.

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 successfully run tests with your changes locally?
• Have you created a changelog file by running pnpm nx affected --target=changelog?

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.

[github-actions]

Hi @claudiosanches, thanks for merging this pull request. Please take a look at these follow-up tasks you may need to perform:

• Add the release: add testing instructions label

[adrianduffell]

@ObliviousHarmony @claudiosanches Do we need another PR to apply this to trunk too?

[ilyasfoo]

Re-ping @ObliviousHarmony as I think we'd need to have this in trunk as well

[ObliviousHarmony]

Sorry, yes, we do. We should set it to 6.6.0.