JOC Cockpit search does not properly handle escaped DBMS wildcard characters

Current Situation

• JOC Cockpit provides several search functions (e.g. Advanced Filter, Quick Search in the Inventory tree, Inventory search).
• These searches support glob patterns:
  • ? matches any single character
  • * matches zero or more characters
• Glob metacharacters are translated into DBMS wildcard operators:
  • ? -> _
  • * -> %
  • This translation does not account for escaping of literal wildcard characters (e.g. _ , %) themselves.
• The issue occurs when searching for literal wildcard characters such as underscore , which are not escaped.
  • Example:
    • Searching for test_ is converted to test_%, resulting in matches for all values starting with test instead of the intended literal prefix test_.

Desired Behavior

• All glob-pattern-based searches must correctly escape DBMS wildcard characters to ensure that literal input is handled accurately.

Test Instructions

• Create all available object types (workflows, jobs, schedules, etc.) using underscore characters (_) in their names.
• Perform tests across all available search functions to verify that these objects can be found exactly according to the search string.
• Additionally, test the FILE TRANSFER search to find Source/Target File Paths containing underscore characters.
• Execute all tests across all supported database systems.