Feature/issue 90 process case

[ciozi137]

Summary

This PR addresses Issue #90 by making process name matching case-insensitive to align with LabVIEW's behavior when recognizing overrides.

Problem

LabVIEW recognizes overrides regardless of case (e.g., both Process.vi and process.vi are valid), but our current implementation was case-sensitive. This mismatch could cause issues when process names didn't exactly match the expected case.

Changes Made

• GetCallingProcessCloneName.vi: Updated to perform case-insensitive matching for Process.vi names
• WaitOnProcessSync.vi: Modified to use GetCallingProcessCloneName.vi for consistent process name resolution, ensuring the same matching algorithm is applied during both registration and synchronization

[Tom-McQuillan]

In principle I am supportive of this.
Although, I am curious why P/process.vi would be spelt differently.
Is it common to create the process vi without using the template tool?

[ciozi137]

@Tom-McQuillan good question. I'm not sure why I ran into this problem. Maybe I had created 'process.vi' and dropped in the template:

Maybe I temporarily renamed it 'DoNotRunProcess.vi' for some other debugging purpose and then inadvertently renamed it 'process.vi' when I switched back.

The main point is that LabVIEW doesn't recognize a difference and wouldn't, didn't, alert the user if the case didn't match. So hoping to save someone else in the future.

I don't know if there is a more elegant fix available instead of: