Alignment configuration free end gaps

[smehringer]

Part of seqan/product_backlog#96

I split the tasks such that the PR doesn't become too large.

Fixes tasks 1 & 2:

• Introduce strong types free_end_gaps_sequence[1/2]_[leading/trailing]
• Make seqan3::method_global a pipeable ocnfig element (not a tag), that is constructible from the 4 strong_types

[codecov]

Codecov Report

Merging #1938 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1938   +/-   ##
=======================================
  Coverage   97.88%   97.89%           
=======================================
  Files         261      262    +1     
  Lines        9831     9865   +34     
=======================================
+ Hits         9623     9657   +34     
  Misses        208      208           

Impacted Files	Coverage Δ
...qan3/alignment/pairwise/alignment_configurator.hpp	100.00% <ø> (ø)
...e/seqan3/alignment/pairwise/detail/type_traits.hpp	100.00% <ø> (ø)
...ring/detail/simd_match_mismatch_scoring_scheme.hpp	100.00% <ø> (ø)
...ment/scoring/detail/simd_matrix_scoring_scheme.hpp	100.00% <ø> (ø)
...n3/alignment/configuration/align_config_method.hpp	100.00% <100.00%> (ø)
include/seqan3/range/views/kmer_hash.hpp	100.00% <0.00%> (ø)
include/seqan3/range/views/minimiser_hash.hpp	100.00% <0.00%> (ø)
...ude/seqan3/range/detail/random_access_iterator.hpp	100.00% <0.00%> (ø)
...de/seqan3/range/container/bitcompressed_vector.hpp	100.00% <0.00%> (ø)
...n3/search/dream_index/interleaved_bloom_filter.hpp	100.00% <0.00%> (ø)
... and 4 more

---

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 60ec68e...d58bebc. Read the comment docs.

[Irallia]

LGFM, thank you!

[eseiler]

This probably does affect users?
If so, add a changelog entry (except it was added after the last release).
BTW, we do not have [NOP] labels for commits :D

[smehringer]

This probably does affect users?
If so, add a changelog entry (except it was added after the last release).

I will add one with the last PR for free end gaps. since right now the change would say
make method_global to method_global{} but after the last PR it will be
make method_global | aligned_ends{free...} to method_global{free...}. I think the in between won't need to be mentioned?

[eseiler]

Do you want to rebase or should I squash?