Stabilize the fingerprint

[tuxu]

Remove the line number from fingerprint. If the same fingerprint is already used for another issue in the same file, generate another one. This is more stable compared to the line number itself, which changes whenever code is added or removed above the issue.

[soul-catcher]

Thank you for opening pull request!

But I think adding a line of code to fingerprint is not an optimal solution for several reasons:

1. If there are multiple duplicate lines in the code, only one warning will be displayed.
2. This solution does not work in cases where the line of code is changed without affecting the problem (for example, after automatic formatting)

Also this adds requirement to have access to source code files.

I decided to look at how other tools, such as Ruff, solve this problem, and found them solution really elegant.

Fingerprint is based on:

1. Error message
2. File path
3. Fingerprint of the previous issue with this path and error message.

I think this is the best way. Could you implement it in this pull request?

[tuxu]

@soul-catcher Thanks for the feedback! I just adapted this PR. The error level and code are kept in the fingerprint to hash the full message.

[soul-catcher]

I checked this in my private Gitlab repo and it works perfectly! Thank you!

[tuxu]

Awesome. Thanks for merging and creating a new release!