Update: Mark no-assert-equal and no-assert-ok as deprecated

[platinumazure]

Replaced by no-loose-assertions, which covers these rules but is also more flexible.

[coveralls]

Coverage remained the same at 100.0% when pulling c95fe32 on deprecate-old-loose-assertions into fce1e12 on master.

[platinumazure]

@bmish Would you mind reviewing this? I added some logic around marking rules as deprecated (and replaced by others), curious if you think I could improve it.

[bmish]

Let's follow the format of the other messages by starting this with an emoji: ❌

[bmish]

Let's add a link to the deprecated section of the README in the README word.

[bmish]

I think we need to improve no-loose-assertions before it will be ready to replace the other two rules:

• It doesn't properly handle globals (similar to Only detect true globals in no-global-* rules #132) -- this is a blocker
• The automatic suggestions from no-assert-equal need to be ported over to it

I can work on this fixing these issues in the coming weeks.

We would then want to make no-loose-assertions recommended as part of the V7 release (#175).

CC: @raycohen about this move to consolidate on no-loose-assertions.

[platinumazure]

I had forgotten about marking no-assert-equal as recommended. That does make things a bit more complicated. Managed to miss that in the Project as well.

I'll make a post in the 7.0.0 issue about how we want to handle this.

[platinumazure]

I'm removing this from 7.0.0 and considering this on hold for now. We can't deprecate until no-loose-assertions properly handles globals.

I would love to get the "infrastructure" for deprecated rules in at some point, but that doesn't have to happen in 7.0.0 nor in this PR.