Adapt the check for hashes in versions

[mzuehlke]

From checking if the complete version value is a hash to only checking if it contains a hash (at least 8 characters long).
The hash component detected by the parser only requires 6 byte, but in addition some leading separator.

Fixes #2502
Improves predecessor #2498
Original issue #2483

[codecov]

Codecov Report

Merging #2522 (50fa42a) into main (1990928) will increase coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #2522      +/-   ##
==========================================
+ Coverage   81.01%   81.09%   +0.08%     
==========================================
  Files         143      143              
  Lines        2518     2534      +16     
  Branches       46       51       +5     
==========================================
+ Hits         2040     2055      +15     
- Misses        478      479       +1     

Impacted Files	Coverage Δ
...ain/scala/org/scalasteward/core/data/Version.scala	100.00% <100.00%> (ø)
...rg/scalasteward/core/edit/hooks/HookExecutor.scala	90.78% <0.00%> (+1.13%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1990928...50fa42a. Read the comment docs.

[exoego]

LGTM

[fthomas]

The fun isn't over yet: davegurnell/unindent#69 :-)

[mzuehlke]

from 7d2bf0af+20171218-1522 to 7e30aec7

This is an update from a version with a hash to another version with a hash.
So versions that are only a hash are worse then versions that only contain a hash (in addition to other numbers) 🤔

[fthomas]

Maybe we should just ignore versions that start with a hash. A bump like 7d2bf0af+20171218-1522 to 8d2bf0af+20171218-1522 would not make any sense either, although both versions contain other numbers besides the hash.