C#: Update Roslyn nuget dependencies.

[michaelnebel]

In this PR we

• Update the Roslyn dependencies to the newest version available.
• Furthermore, we change the strategy for getting package version to use the newest available version <-- Note that this only happens when we explicitly update the dependencies using the update_deps.sh script as this creates a lock file that locks packages to a specific version number. The motivation for this is because we got the compiler warning: GHSA-xhfc-gr8f-ffwc (which is most likely because one of the transitive dependencies is using it).

Comments to the updated expected test output.

• There appears to be an improvement to Roslyn, which means that the call target of new() is correctly extracted.
• The format test expected output is updated as the params keyword is correctly extracted.
• The parameters test is limited to inspect only source code (a feature of C# 13 is that params is now supported for a wide range of collection types). https://learn.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-13#params-collections

There was an issue with the binary log extraction (it could be reproduced outside the extractor). jaredpar/complog#187. This was quickly fixed and a new version of the binlog package is now referenced instead.

DCA:

There doesn't appear to be any performance regressions or changes to the security related alerts, but there is an increase in the number of compilation errors.
I looked into the compiler errors for dotnet/runtime and dotnet/roslyn. It appears that there are two categories of errors.

• Compiler errors related to the use of field within property accessors.
• Compiler errors related to not having interceptors enabled.

Both of these features are preview features (I checked that preview features are enabled for dotnet/runtime). The SHAs of the projects analyzed are pretty old. Roslyn yields compilation errors because

• A variable (or parameter) named field is used within an property accessor (as this references the backing field of the property, when preview features are enabled). https://learn.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-13#the-field-keyword
• Enabling interceptors now uses InterceptorsNamespaces instead of InterceptorsPreviewNamespaces, which can explain the compiler errors related to interceptors: dotnet/roslyn@5758964#diff-eef9e4c724788e9db96f07567a9894bbb2da020ec59a2ded58b7f22bd175a1a1R223