Release automation uses incorrect destination

[aaemnnosttv]

Bug Description

The release automation we have in place currently sits within our zips workflow which builds zip files for PRs and the latest builds for our main branches. The zip file is structured the way WP expects: including the plugin's directory, however the release does not account for this so it ends up adding the files in the wrong (nested) destination.

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• The publish-to-wporg GHA job should be updated so that it sources the contents to deploy from the unzipped built plugin, without including the root google-site-kit directory

Implementation Brief

• [ ] Update the action-wordpress-plugin-deploy step to include the BUILD_DIR env variable, defined to target ./google-site-kit (the root directory). This should set the source that is synchronized into trunk to use the contents rather than the more complicated logic based on .distignore or .gitattributes
• [ ] The line to create a .distignore in the Extract step can then be removed

Test Coverage

• No changes as actions don't have tests

QA Brief

• N/A

This will need to be tested by running the release automation task, I don't see another way it can be tested 🤔

Changelog entry

• N/A

[binnieshah]

@aaemnnosttv could we get an estimate for this one, I am trying to see if we can get this into the next sprint. Thanks

[eugene-manuilov]

IB ✔️

[eugene-manuilov]

Moving to Approval since there is nothing to test.

[aaemnnosttv]

Tested with a dry run here and looks great 🎉