Inventory search - advanced search "Exact Match for Job Name" may return incorrect results

Current Situation

• The Inventory advanced search using the Exact Match for Job Name filter should search for the exact job name without left or right truncation.
• However, the search behavior differs depending on the underlying JOC Cockpit database:
  • Oracle
    • Returns exact matches correctly, for example:
      • myjob -> finds workflows with myjob only
      • MyJob -> finds workflows with MyJob only
  • MySQL / MSSQL with case-insensitive database collation - incorect behaviour
    • When searching for MyJob, results for workflows with the lowercase job name myjob are returned if such workflows exist due to case-insensitive collation handling.
  • PostgreSQL - incorect behaviour
    • When searching for MyJob, no result is returned, even if a workflow with myjob exists.

Desired Behaviour

• The Exact Match for Job Name filter should work correctly and consistently across all supported databases.

Test Instructions

• Create two workflows:
  • The first workflow should use a job with a lowercase name, for example myjob
  • The second workflow should use a job with uppercase characters in the name, for example MyJob
• Test the Inventory advanced search using all supported databases:
  • with activated Exact match for Job Name
  • without activated Exact match for Job Name
• MySQL / MSSQL Tests
  • 2.8.4-SNAPSHOT
    • The MySQL database should use a non-binary collation: utf8_general_ci
      • This was the JS7 default for MySQL setups before JOC-2207.
    • The MSSQL database should use a non-binary collation: LATIN1_GENERAL_100_CI_AS_SC_UTF8
      • This was the JS7 default for SQL Server setups before JOC-2207.
  • 2.9.0-SNAPSHOT
    • MySQL and MSSQL should use binary collations according to JOC-2207.