…simplifying a bunch of it

This has always annoyed that we had to cast this, so thought I'd twaek it while we're here.

* Update dependencies from https://github.com/dotnet/arcade build 20260204.6
On relative base path root
Microsoft.DotNet.Arcade.Sdk From Version 10.0.0-beta.26080.4 -> To Version 10.0.0-beta.26104.6

* Update dependencies from https://github.com/dotnet/arcade build 20260206.4
On relative base path root
Microsoft.DotNet.Arcade.Sdk From Version 10.0.0-beta.26080.4 -> To Version 10.0.0-beta.26106.4

* Update dependencies from https://github.com/dotnet/arcade build 20260210.1
On relative base path root
Microsoft.DotNet.Arcade.Sdk From Version 10.0.0-beta.26080.4 -> To Version 10.0.0-beta.26110.1

---------

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

…inal and generated document positions (#12772)

* Modify RazorCSharpDocument to keep sourcemappings sorted by both Original and Generated document indices

This class previously just kept an array that was sorted by generated positions. Many callers would benefit instead from an array sorted by original (html) posititions. This allows many loops to short-circuit once they've moved beyond any mappings that could be of interest to them.

This also renamed the original array to indicate it's sorted by generated positions, and to validate that upon it's input, as some callers were assuming that. By renaming this variable, it will hopefully make callers

1) Aware that the input is sorted and may be short-circuited or binary searched
2) Aware what it is sorted by (eg: formatting had some code that was assuming the array was sorted by original position)

* Be more resilient to bad input

* Use Debug.Fail

* Fix test to do different validation in debug/release