Fix: Handle comparison operators < and <= correctly in OSLC Where clause

[berezovskyi]

Description

If a query has <=, e.g. <=42, it is incorrectly treated as a URI, which will never succeed.

OSLC Query support is not very well tested, would be hard to verify this for regressions. Unit tests were added to cover the change.

Checklist

• This PR adds an entry to the CHANGELOG. See https://keepachangelog.com/en/1.0.0/ for instructions. Minor edits are exempt.
• This PR was tested on at least one Lyo OSLC server (e.g. manual workflow on Lyo Sample and OSLC RefImpl) or adds unit/integration tests.
• This PR does NOT break the API

Issues

Closes #43

(use exactly this syntax to link to issues, one issue per statement only!)

[Copilot]

Pull Request Overview

This PR fixes a bug in the OSLC Where clause parser where comparison operators < and <= followed by numeric values were incorrectly being parsed as URI references instead of comparison operations. The fix ensures that URI references must start with an alphabetic character after the opening < to avoid conflicts with comparison operators.

• Modified the ANTLR grammar to require alphabetic characters after < for URI references
• Added comprehensive unit tests to verify correct parsing of < and <= operators with various operand types
• Applied code formatting improvements to align with project style guidelines

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

File	Description
OslcWhere.g	Updated ANTLR grammar rule to require alphabetic characters in URI references, preventing conflicts with comparison operators
BasicWhereTest.java	Added extensive unit tests for < and <= operators with integers, strings, URIs, and edge cases, plus code formatting improvements

[berezovskyi]

@oslc-bot /test-all

[oslc-bot]

Downstream Build Status

Repository	Lyo CI	Job state	Workflow
oslc-op/refimpl	✅ Pass	completed	Link
oslc/lyo-samples	✅ Pass	completed	Link
oslc/promcode-lyo-server	✅ Pass	completed	Link