fix: fixed column filters in job list and job history tables

[plakkara-bc]

Job Monitoring Filter Consistency and Trigger By Fix

This PR addresses filter inconsistencies in Job Monitoring, starting with the Trigger By column issue and then aligning Job Name filter behavior between Job List and Job History.

Problem 1: Trigger By filter values were incorrect

• AC expected Trigger By filter values to represent:
  • SYSTEM
  • specific end-user IDIRs (for example CGWRK22)
• Actual behavior showed SYSTEM and a generic USER, which was not aligned with requirements.

Fix 1: Trigger By filter options updated

• Replaced static Trigger By options with dynamic values derived from monitoring data.
• Trigger By LOV now shows:
  • SYSTEM first
  • followed by discovered IDIR values (sorted)
• Applied consistently to both:
  • Job List Trigger By filter
  • Job History Trigger By filter
• Updated matching logic to handle case-insensitive comparisons safely.

Problem 2: Job Name filter behavior was inconsistent

• Job History Job Name used LOV dropdown.
• Job List Job Name used free-text filter.
• Same field had different UX patterns.

Fix 2: Job Name filter behavior made uniform

• Changed Job List Job Name filter from text input to LOV dropdown.
• Reused the same monitored Job Name option set as Job History.
• Updated Job List Job Name filtering to exact LOV selection behavior (not substring text search).

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Automated/Unit tests
• Manual tests (description below)
• No new tests are required

Checklist

• I have tested my changed locally
• The code builds and pass all tests, No warning
• I have made corresponding changes to the documentation

In Progress/Follow Up

[mdiapenabc]

Job Name filter uniformity looks good.

For Trigger By: good fix replacing USER with actual IDIR values, but triggerOptions is derived only from loaded rows (Job List latest-per-type ~6 rows + Job History current page). Since Job History filters over 1 month server-side, users may not be able to filter by valid IDIRs unless that IDIR happens to be on the current page. Please source distinct Trigger By values from the full 1-month monitoring scope

Minor: remove unused USER branch in matchesTriggerFilter.