empty-comment line number bug fix

[orSolocate]

Steps

• Add yourself to CONTRIBUTORS if you are a new contributor.
• Add a ChangeLog entry describing what your PR does.
• If it's a new feature or an important bug fix, add a What's New entry in doc/whatsnew/<current release.rst>.
• Write a good description on what the PR does.

Description

Fixed empty-comment wrong line number in its message. Was 1 line behind the actual line number.
Fixed implementation and unittest.

Type of Changes

	Type
✓	🐛 Bug fix
	✨ New feature
	🔨 Refactoring
	📜 Docs

Related Issue

#4009

[coveralls]

Coverage remained the same at 90.681% when pulling 5b109b4 on orSolocate:empty_comment_bug_fix into b41e8d9 on PyCQA:master.

[coveralls]

Coverage decreased (-0.008%) to 90.673% when pulling 5b109b4 on orSolocate:empty_comment_bug_fix into b41e8d9 on PyCQA:master.

[Pierre-Sassoulas]

Thank you for this fix, it seems pretty straightforward. Could you just add a functional test in tests/functional/e/empty_comment.py, please ?

[Pierre-Sassoulas]

Hmm, sorry, what I asked for is impossible as functional test need non empty comments to work.

[Pierre-Sassoulas]

I merged it, your change will be available when we release 2.6.1 or 2.7.0 (soon!) :) ! Congrats on becoming a pylint's contributor !

[orSolocate]

@Pierre-Sassoulas Thanks for accepting it. Hopefully more contributions will follow :)