Always reactivate the plugin after tests

[BrianHenryIE]

Moves the activate plugin code from the end of each test case into the afterEach() method.

Otherwise, when an individual test fails, the plugin is not reactivated and subsequent tests fail where they expect it to be loaded. afterEach() always runs, like try-catch-finally.

Cypress highlights this as an anti-pattern in their best practices guide. It should be done in a before/beforeEach but that would require updating all test suites which could possibly run after this one.

[circlecube]

I think we'd need to update the tests here to work a bit differently if adding an afterEach. Some of the steps don't disable the plugin so on those wouldn't this error since there isn't an activate link when it's already active.

Alternatively, we could use a CLI command to activate - probably takes a little longer to run, but should always work.

[BrianHenryIE]

OK, I'll take another look. I thought since cy.get().then({}) doesn't perform an assertion, it woudn't fail when there is no activate button, and would only run the then closure when there is a deactivate button. I see the failing tests there, though.

[circlecube]

Looks like it is still failing with the if seems like the find inside the if will still cause the test to fail?

[circlecube]

I'll close this out since #8 should resolve the issue by reactivating the plugin after these tests via a cli command.