Update manually the cecil version

[tlakollo]

The current version has a bug that prevents the illink package to generate valid IL.
The Microsoft.NET.ILLink.Tasks package is blocking runtime to SDK flow
There is a PR #80429 that updates the cecil dependency into runtime but its blocked due to failures (there is 10 different repos trying to be updated at the same time)

[ghost]

Tagging subscribers to this area: @agocke, @sbomer, @vitek-karas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The current version has a bug that prevents the illink package to generate valid IL.
The Microsoft.NET.ILLink.Tasks package is blocking runtime to SDK flow
There is a PR #80429 but its blocked due to failures

Author:	tlakollo
Assignees:	tlakollo
Labels:	area-Tools-ILLink
Milestone:	8.0.0

[tlakollo]

@dotnet/runtime-infrastructure is it ok to manually update this dependency?

[MichalStrehovsky]

You'd also need to update the version in Versions.props. The Version.Details.xml doesn't do anything based on my past experience.

[ViktorHofer]

#80429 should now be unblocked and could be merged into main in roughly 3 hours. Let's wait for that one to avoid a merge conflict.

There is 10 different repos trying to be updated at the same time

Usually those dependency updates are less noisy, i.e. runtime-assets or hotreload-utils, etc. But we also batched roslyn updates into it and those are more complex and create more noise from what I perceived in the last weeks. I just changed that so that roslyn updates open a separate PR.

[ViktorHofer]

Closing in favor of #80429