Ensure the publish/save button isn't disabled before clicking on it

[dkotter]

Description of the Change

As described in #115, the classicCreatePost command can sometimes fail if autosaving takes too long. When an autosave happens, WordPress adds the disabled class to the publish button. Once autosave is done, that class is removed. But if our test runs quicker than the autosave, we try clicking the button and nothing happens and our test then fails because the savePost alias never fires.

This PR attempts to fix that by ensuring this button does not have the disabled class before we try clicking it

Closes #115

How to test the Change

Run a test that uses the classicCreatePost command and ensure it works as expected

Changelog Entry

Fixed - Ensure the publish button isn't disabled before we click it in the classicCreatePost command

Credits

Props @dkotter

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.

[faisal-alvi]

Thank you for the efforts @dkotter!

LGTM. I've conducted another round of testing on the PR in the forked repository, and classic-create-post.test.js is also passing there.

However, it's worth noting that a few other tests (for WP latest and WP trunk) are failing in both PRs. These failures seem unrelated to the current PR and already failing in the develop branch too, so I assume we can proceed with merging this one first and worry about the others later.