Fix CustomCcmRule to drop CURRENT flag no matter what

[dkropachev]

It is follow up for #1720

If super.after() throws an Exception CURRENT flag is never dropped which leads next tests with CustomCcmMRule to fail with IllegalStateException("Attempting to use a Ccm rule while another is in use. This is disallowed")

[dkropachev]

@lukasz-antoniak , @tolbertam, could you please take a look at it

[tolbertam]

Thanks for the follow up on this @dkropachev, agreed on this change.

ccm remove failing (in super.after()) may indicate some odd/fatal state, but I agree that not resetting CURRENT assuredly leaves things in a state where further tests can't possibly run and it makes sense to make a best effort to allow tests proceed 👍

[absurdfarce]

Agree that the current behaviour is incorrect; an exception in super.after() shouldn't lead to subsequent failures. I've kicked off a Jenkins run to make sure there isn't any unexpected regression here (I'll be very surprised if there is) so once that's complete with issue this gets a +1 from me.

[absurdfarce]

Jenkins run looks good: one test failure but it's from a test that's known to fail intermittently.

[tolbertam]

Thanks for the review and the testing @absurdfarce!

@dkropachev, if you could, can you amend your commit to include this in the last line and force push? Otherwise if you can give me access to the branch I can amend it as well:

Patch by Dmitry Kropachev; reviewed by Andy Tolbert and Bret McGuire for JAVA-3117

(Reusing JAVA-3117 as this was a follow on). After that I'll merge it, thanks!