Field 'Target Files' is not case-insensitive

[tjgalama]

When I set the field value 'azuredeploy.parameters.BCO.json' in this field, the existing file with the name 'azuredeploy.parameters.bco.json' is not recognized. As a result the file is not patched (and continues without an error using the definition's default settings) When it concerns fields with 'file'-values, most other tasks definitions are case-_in_sensitive. I expect this field to behave equally

[sandorfr]

Linux file system is not case insensitive and the task is intended to work on both systems in a predictable way.

I might consider an option to make it case insensitive.

[mwaldron14]

I would also love to see an option to make the "Target Files" case insensitive. Maybe a checkbox for this as an option? Thanks for your consideration! :)