Allow ranges for excluded_sequences config option

[ljoss17]

Closes: #4047

Description

This PR changes the type of excluded_sequences in the configuration to be a ExcludedSequences which has custom serialisation and deserialisation. This allows the usage of ranges of sequences in addition to exact values.
It is now possible to specify excluded sequences using:

• Exact values, e.g. [1, 2, 3]
• Range with "..=", e.g. ["1..=3"]
• Range with "..", e.g. ["1..3"]
• Range with "-", e.g. ["1-3"]

These 4 examples will result in the same result.

---

PR author checklist:

• Added changelog entry, using unclog.
• Added tests: integration (for Hermes) or unit/mock tests (for modules).
• Linked to GitHub issue.
• Updated code comments and documentation (e.g., docs/).
• Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

• Reviewed Files changed in the GitHub PR explorer.
• Manually tested (in case integration/unit/mock tests are absent).

[romac]

I am a bit wary of supporting both .. and ..= with the same semantics, given that in Rust these mean exclusive and inclusive upper bound, respectively. Granted, it's probably not common knowledge outside of Rust programmers.

Still, I would rather we keep a single syntax for defining ranges. How about keeping only -, as it does not collide with Rust ranges, and does not require users to ponder about whether or not it's inclusive or exclusive, provided that we make it explicit in the config file.

What do you think @ljoss17?

[romac]

See comments above. Great job otherwise!

[ljoss17]

I am a bit wary of supporting both .. and ..= with the same semantics, given that in Rust these mean exclusive and inclusive upper bound, respectively. Granted, it's probably not common knowledge outside of Rust programmers.

Still, I would rather we keep a single syntax for defining ranges. How about keeping only -, as it does not collide with Rust ranges, and does not require users to ponder about whether or not it's inclusive or exclusive, provided that we make it explicit in the config file.

What do you think @ljoss17?

I agree, having a single separator will make it cleaner. Yes the - seems the best option.