Raise SearchQueryParseError when HybridRetriever and HybridCypherRetriever encounters invalid Lucene string

[willtai]

Description

This PR introduces SearchQueryParseError that gets raised when HybridRetriever and HybridCypherRetriever encounters invalid Lucene string.

For example, ~alien should raise an error as this is as the reserved character ~ is used incorrectly.

However, "alien~" is valid and should neither raise an error nor get processed (see Apache Lucene documentation).

Type of Change

• New feature
• Bug fix
• Breaking change
• Documentation update
• Project configuration change

Complexity

Complexity: Low

How Has This Been Tested?

• Unit tests
• E2E tests
• Manual tests

Checklist

The following requirements should have been met (depending on the changes in the branch):

• Documentation has been updated
• Unit tests have been updated
• E2E tests have been updated
• Examples have been updated
• New files have copyright header
• CLA (https://neo4j.com/developer/cla/) has been signed
• CHANGELOG.md updated if appropriate

[willtai]

@CodiumAI-Agent /update_changelog

[CodiumAI-Agent]

Changelog updates: 🔄

[2025-02-26][https://github.com//pull/286]

Added

• Introduced SearchQueryParseError for handling invalid Lucene query strings in HybridRetriever and HybridCypherRetriever.

to commit the new content to the CHANGELOG.md file, please type:
'/update_changelog --pr_update_changelog.push_changelog_changes=true'