Wildcard support added

[Thorium]

Fixes #776

[knocte]

Thanks @Thorium good work! Just from a quick glance, can you:

1. Fix CI build please. It's again failing in the SelfCheck step, those issue are easy to address IMO, ping me if you need help.
2. Can you add some kind of warning when using this command line option? Because it's still recommended/preferable that users use their solutions or projects, rather than individual files, because this way FSharpLint can act on the typed tree (and discover more warnings than if it were running on an untyped one).

[Thorium]

Will check. The 2 major use-cases I have:

1. I have a group of fsx files in random directory structure to check. There is no project.
2. I have installed .NET10 runtime to a computer and global.json missing from a project, so FSharpLint fails for System.Runtime v10 errors.

[knocte]

I have a group of fsx files in random directory structure to check. There is no project.

Ah, maybe if the wildcard ends with .fsx then it should not show a warning, since fsx files are generally not in a project. But things like *.fs, *.fs?, *.fs*, foo.fs should give a warning.

[Thorium]

I think the warning is still ok to show: The best practice is not work with big bunch of fsx files because the compiled F# is faster.

[knocte]

Merged, you can already use this feature if you grab this pre-release version from nuget:
0.26.5--date20251110-0458.git-33ee73e