Decrement Enzyme compatibility

[bauglir]

It looks like the compat for Enzyme may have been incorrectly updated in the v0.2 release branch given that compatibility is still indicated to be with v0.11 on master. I'm running into a situation where I cannot resolve an environment that happens to pull in Enzyme for different packages due to this restriction.

I hope it's okay to bump this compat back down so we're able to resolve environments like this with the v0.2 release branch. I have completely dropped the v0.12 compatibility here as it's also not marked as compatible on master as mentioned above.

[Red-Portal]

I actually wonder if we want to restrict the compat bound for Enzyme at all given that we don't test on Enzyme. @torfjelde How about just removing the compat bound entirely?

[bauglir]

How about just removing the compat bound entirely?

I would be fine with either, but I'm not sure whether automerge on the General registry requires compats to be defined for weak dependencies as it does for regular dependencies. If it does, it's probably easier to maintain the compat as otherwise all releases of this package would have to get manually merged.

[Red-Portal]

Okay, let me first check that.

[bauglir]

From a quick glance at the automerge guidelines it looks like the compat requirements are (currently) only applied to strict dependencies and not to weak dependencies.

At the moment the aren't any references to weak dependencies in automerge guidelines. So it looks like it might be okay to not include a compat from that perspective at least.

[Red-Portal]

I asked around, and authorities do say that compat rules are also enforced to weakdeps. So even if it is not enforced, I think just bumping the bound down would be the formal solution.

[bauglir]

Sounds good to me.