feat(alarms): Support filtering alarms by source

[Ahalya-ni]

Pull Request

🤨 Rationale

User Story 3283281: FE | Handle filter transformation in Query builder
Task 3249469: Add source filter support to alarms query builder

This PR adds support for source filtering in the alarms query builder component.

👩‍💻 Implementation

• Added a source constant to AlarmsQueryBuilderFields, including its data field, label, and supported filtering operators.
• To support filtering, since source must be accessed within the properties object, any filter using source is transformed to the format: properties.system <operator> <value> || properties.minionId <operator> <value>.
• Created a file called SourceProperties.constant to store the custom properties for reusability.
• Exported the method from utils.ts previously named getLogicalOperator to be used for combining system and minionId expressions.
• Moved getLogicalOperator below multipleValuesQuery since it is now a public method; this file is organized with public methods at the top and private methods below.
• Renamed getLogicalOperator to getFilterConcatOperator to better reflect its purpose, as it is used for combining multi-value expressions (e.g., {value1, value2}) as well as conditions like those used for source (system and minionId expressions).
• Updated the getFilterConcatOperator to return logical OR for isnotblank operator as its transformation logic is already in place.

Another approach

Another approach I considered was introducing separate query builder operators to handle source-related transformations directly within the expression builder callback of the query builder. This alternative did work, but it has a drawback: the resulting source expressions (such as (properties.system = "test-source" || properties.minionId = "test-source")) are not parsed by the query builder, which leads to an empty expression in the reader callback. For more details, refer to the prototype and the relevant branch.

🧪 Testing

Added unit tests

✅ Checklist

• This PR has a title that follows the commit message format.