fix(job_attachments): handle case-insensitive path extraction on Windows

[gahyusuh]

What was the problem/requirement? (What/Why)

On Windows, asset paths are not treated as case-insensitive, leading to incorrect grouping of assets with paths that differ only in case. For example, if two paths "C:\Username\user\test1.txt" and "c:\uSerNaMe\user\test2.txt" exist, their shared root path should be extracted as "C:\Username\user". However, currently, these paths are treated as having different root paths due to the case-sensitivity issue.

What was the solution? (How)

The _get_asset_groups function has been modified to ensure that the root path extraction is case-insensitive on Windows.

What is the impact of this change?

Resolves the issue of incorrect asset grouping on Windows due to case-sensitivity

How was this change tested?

• A new unit test case has been added to validate the case-insensitive root path extraction.
• Existing unit tests and integration tests pass successfully.
• Manual end-to-end testing: submitting a job with a following parameter:

  name: AssetsDir1
  type: PATH
  objectType: DIRECTORY
  dataFlow: IN
  default: ./INPUTS_1
  

Where the actual input directory's name on the file system is inputs_1. The job submission and job execution on a worker was working, and generated output files as expected.

Was this change documented?

No.

Is this a breaking change?

No.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[loachri]

LGTM! Ship it