[release/10.0] Address upcoming breaking change for span-valued collection expressions (#120774)

Backport of #120771 to release/10.0

/cc @RikkiGibson

## Customer Impact

- [ ] Customer reported
- [X] Found internally

Customers could end up with incorrect behavior due to the backing
storage for a collection expression having the wrong lifetime relative
to the local that tracked it.

## Regression

- [ ] Yes
- [x] No

C# took a late breaking change to fix a lifetime issue around collection
expressions and the IL it was emitting. This behavior has been around
since collection expressions were introduced.

## Testing

Explicit validation of the IL was done.

## Risk

Low. This is the only place in the repo that was impacted by the break
and was updated to use an appropriate lifetime for the collection
expression.

Co-authored-by: Rikki Gibson <rigibson@microsoft.com>

Author: github-actions[bot]

src/libraries/System.Numerics.Tensors/src/System/Numerics/Tensors/netcore/TensorShape.cs

@@ -68,10 +68,10 @@ internal enum TensorFlags : uint
         private TensorShape(nint linearLength, scoped ReadOnlySpan<nint> lengths, scoped ReadOnlySpan<nint> strides, TensorFlags flags)
         {
             int rank = lengths.Length;
-
+            ReadOnlySpan<nint> rank0Lengths = [0];
             if (rank == 0)
             {
-                lengths = [0];
+                lengths = rank0Lengths;
                 rank = 1;
             }
             Debug.Assert(rank >= 1);