Add composer autoload

[MaxwellGarceau]

Description of the Change

Added autoloading to have an easy way to modularize new code and refactor existing code in the future.

❗I modified the Github action workflow files to install composer dependencies in order to ensure autoload was being generated on every build. I wanted to flag this in case I missed a required build process update.

Also, if there's a good place to add documentation for in progress pattern updates I'd be happy to add switching to autoload in new work and any refactors.

Closes #96

How to test the Change

Changelog Entry

Developer - Add Composer autoload.

Credits

Props @username, @username2, ...

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added tests to cover my change.
• All new and existing tests pass.

[dkotter]

Overall this looks good but we'll need to do a few more things:

1. We have a GitHub Action that deploys plugin assets and readme changes. That will need to be updated to run composer install as well
2. We don't currently deploy the vendor directory so we'll need to update that or things won't work in the final release. We have both a .distignore and .gitattributes files that will need updated

[MaxwellGarceau]

Overall this looks good but we'll need to do a few more things:

1. We have a GitHub Action that deploys plugin assets and readme changes. That will need to be updated to run composer install as well
2. We don't currently deploy the vendor directory so we'll need to update that or things won't work in the final release. We have both a .distignore and .gitattributes files that will need updated

@dkotter I've made the requested changes.

1. Updated .github/workflows/wordpress-plugin-asset-update.yml with the composer install and autodump commands
2. Removed the vendor folder from distignore and gitattributes

Note: I've updated the translators comment to match an example I found in WP Core.

[qasumitbagthariya]

QA Update ✅

---

• Run composer install to install dependencies and generate the autoload files. (Composer version 2.8.4) ✅

• Verify that the vendor/autoload.php file is generated. ✅

• Verify Functionality of Existing Features

[qasumitbagthariya]

Regression / Smoke Test Report ✅

Tested with the smoke-testing branch, it works as expected, similar to the fix-specific branch.

Testing Environment

• WordPress: 6.7.1
• Theme: Storefront 4.6.0
• Theme: Twenty Twenty-Four 1.3
• WooCommerce - 9.5.1
• PHP: 8.0.30
• Web Server: Nginx 1.20.2
• Browser: Chrome
• OS: macOS 15.2
• Branch: smoke-testing

[dkotter]

@vikrampm1 @MaxwellGarceau E2E tests are failing here. Not sure if that is specific to the changes made here or something else but in getting merge conflicts cleaned up here to get this merged in for release, I think we should get those fixed up before we proceed, otherwise we'll need to fix those anyway on that release PR.

[vikrampm1]

@dkotter got it. @iamdharmesh can you able to assist with the above as @MaxwellGarceau is not resourced on this project anymore?

[iamdharmesh]

@dkotter E2E tests were failing because we are using the build release action from the develop branch, and it doesn't have the composer installation step. Due to an early return in the autoload file check, the plugin functionality was not getting enabled. I temporarily pointed the build release action to this PR, and it started working as expected.

However, we recently enabled 2FA on the OSP account, and because of this, the connection tests and tests requiring connections are failing. I tried running the tests locally with a different account, and they worked well. So, it seems we are good to proceed here.

cc: @vikrampm1