Allow assemblyfilters/filefilters to be case insensitive

[nikosatwork]

Describe the bug

It appears that DefaultFilter's excludeFilters/includeFilters are case sensitive. It would be great if there was an option to disable that and allow any case to be matched in the regex

To Reproduce

when there is an assembly named Some.Assembly in your code, if you pass
-assemblyfilters:+Some.* then Some.Assembly will be included in the report
however, if you pass -assemblyfilters:+some.*, Some.Assembly will not be included in the report

[danielpalme]

Instead of changing the implementation, you could also:

• Use several filters: -assemblyfilters:+Some.*;-assemblyfilters:+some.*
• Use wildcards: -assemblyfilters:+*ome.*
• Use a consistent naming scheme for all your assemblies :-)

[manfred-brands]

I agree with @nikosatwork. I have a script that runs coverage and reporting for a specified assembly by name as found on disk (e.g. Some.Assembly).
Either the coverage runner (dotnet) or converter (CodeCoverage.exe) converts the assembly name to lower case in the xml file. I don't know if other runners do the same or not.
Therefore when passing that same 'Some.Assembly' to the ReportGenerator results in an empty report.

I worked around this by explicitly converting the argument to lowercase before passing to ReportGenerator.
It would be nice if ReportGenerator would either convert the filter to lower case if all collectors do that or use case-insensitive comparison.

If you agree, I can modify the code and raise a PR.

[danielpalme]

Fixed in release 4.7.1

[nikosatwork]

Thank you @danielpalme!