Bug fixes for filter ranges

[gaspergrom]

Changes proposed ✍️

What

🤖 Generated by Copilot at 00f22e0

This pull request updates the label rendering and query parsing logic for the number and date filter components in the frontend. It adds support for the FilterNumberOperator.NOT_BETWEEN and FilterDateOperator.NOT_BETWEEN operators, and improves the clarity and consistency of the labels.
​

🤖 Generated by Copilot at 00f22e0

BETWEEN or not
Filtering by date or number
Autumn leaves the valueTo

Why

How

🤖 Generated by Copilot at 00f22e0

• Support the FilterDateOperator.NOT_BETWEEN and FilterNumberOperator.NOT_BETWEEN operators for the date and number filter components in the frontend (link, link, link)
• Modify the numberItemLabelRenderer function in number.label.renderer.ts to prepend the operand text to the value text for the FilterNumberOperator.NOT_BETWEEN operator and remove it for the FilterNumberOperator.BETWEEN operator (link)
• Modify the dateQueryUrlParser and numberQueryUrlParser functions in date.parser.ts and number.parser.ts to check for both the BETWEEN and NOT_BETWEEN operators when parsing the value from the query string or deleting the valueTo property from the filter object (link, link)

Checklist ✅

• Label appropriately with Feature, Improvement, or Bug.
• Add screehshots to the PR description for relevant FE changes
• New backend functionality has been unit-tested.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.