Issue-15: Add GitHub Actions for Testing This Repo

[benpbolton]

Summary

This pull request introduces GitHub Actions to ensure that changes to create-wordpress-plugin and create-wordpress-theme do not break this project. It aims to address the user story and acceptance criteria outlined in the GitHub issue to resolve #15 .

Changes

• Added a new GitHub Action workflow file that runs checks on PRs and on a schedule.
• Configured the workflow to use an automatic installation script to emulate user behavior (selecting all defaults for now) for project configuration.

Notes for reviewers

• GitHub Action should be triggered on PR creation and scheduled weekly
• While the GitHub Action successfully configures the project using the automatic installation script and runs through a 'default' installation, there are several discovered issues (created phpcs and phpunit are not running from the project 'root' #114 for reference):
  • phpcs isn't running from the root (composer.json suggests going into the plugin directory to run, but these should run from root)
  • phpunit isn't running from the root (same deal as above)

... as such, the tests will be failing but we intend to ship this with failing tests and create any necessary follow-up issues to address.

Additional Notes

Per the discussion in the issue comments, testing against both VIP-type and Pantheon-type repos was considered challenging due to the current state of the configure.php script. The decision was made to focus on testing with default options to progress with the implementation of this feature.