Exclude .wordpress-org directory when deploying standalone plugins

[mukeshpanchal27]

Summary

Fixes #850

I have manually tested the standalone workflow on the forked repository. I have generated a zip file for the plugins and attached it to the summary to verify the process. You can check the following URLs and verify the attached zip:

• WebP Uploads
• Dominant Color Images

Checklist

• PR has either [Focus] or Infrastructure label.
• PR has a [Type] label.
• PR has a milestone or the no milestone label.

[felixarntz]

@mukeshpanchal27 Could we use .gitattributes instead of .distignore, the same way we do for the main plugin?

[mukeshpanchal27]

@felixarntz thanks for the feedback. PR is ready for another round of feedback. Thanks! cc. @joemcgill

[felixarntz]

Thanks @mukeshpanchal27, LGTM!

[felixarntz]

@mukeshpanchal27 One thing we should test here is to make sure that the module specific .gitattributes files are not part of the main plugin ZIP. We could probably test that with a dry run of the main release workflow.

[mukeshpanchal27]

Thank you, @felixarntz, for bringing this to my attention. I've conducted testing on the main plugin zip through a GitHub action workflow in the forked repository, and it appears that the plugin is exclude the .gitattributes and .wordpress-org files for the module directories.

You can review the workflow here: GitHub Workflow. Once you download the attached performance-lab file, extract it, and subsequently extract the zip generated by the GitHub action, which is meant to be deployed on WordPress.org, you will notice that these excluded files cannot be found.