Removing the option to have map-kmers hit multiple reference ranges.

[zrm22]

Description

Removing option for users to have Kmers map to different reference ranges. This is identical to how things were done in previous versions of PHGv2

Type of change

What type of changes does your code introduce? Put an x in boxes that apply.

• [x] CHANGE (fix or feature that would cause existing functionality to not work as expected)
• [ ] FEATURE (non-breaking change which adds functionality)
• [x] BUGFIX (non-breaking change which fixes an issue)
• [ ] ENHANCEMENT (non-breaking change which improves existing functionality)
• [ ] NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)

Checklist:

• [x] I have performed a self-review of my code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have updated relevant documentation

Changelog entry

Please add a one-line changelog entry below. This will be copied to the changelog file during the release process.

Removing option to map reads to multiple reference ranges.

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 42.85714% with 4 lines in your changes missing coverage. Please review.

Project coverage is 82.82%. Comparing base (ef0ec75) to head (35548ae). Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
.../net/maizegenetics/phgv2/pathing/AlignmentUtils.kt	20.00%	4 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #217 +/- ## ========================================== - Coverage 82.84% 82.82% -0.02% ========================================== Files 77 77 Lines 5053 5049 -4 Branches 836 835 -1 ========================================== - Hits 4186 4182 -4 Misses 556 556 Partials 311 311 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.