encoded-compare: fix suggestions for JSONEq and YAMLEq

[ccoVeille]

I spotted it by using the following code:

var foo json.RawMessage
assert.EqualValues(t, `{"foo": "bar"}`, foo)

that testifylint suggested fixing like this:

var foo json.RawMessage
assert.JSONEq(t, `{"foo": "bar"}`, foo)

It's invalid because JSONEq expects strings.

Later, I noticed the code was also suggesting to replace (even if it's invalid):

var i int
assert.Equal(t, `{"foo": "bar"}`, i)

with:

var i int
assert.JSONEq(t, `{"foo": "bar"}`, i)

The PR is divided in 2 commits to help to reproduce the issue:

• encoded-compare: add tests to reveal false positives
• encoded-compare: fix suggestions for JSONEq and YAMLEq

[coveralls]

Pull Request Test Coverage Report for Build 15742930669

Details

• 31 of 31 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 93.65%

---

Totals
Change from base Build 14796134649:	0.02%
Covered Lines:	2625
Relevant Lines:	2803

---

💛 - Coveralls