Align Device Bound Sessions package with platform prerelease versioning

`Microsoft.AspNetCore.Authentication.DeviceBoundSessions` currently uses `$(ExperimentalVersionPrefix)`, which produces versions such as:

```text
0.11.0-rc.1.26425.128
```

This differs from the versioning used by packages that ship with the ASP.NET Core release but intentionally remain prerelease, such as `Microsoft.AspNetCore.Components.Media` and `Microsoft.AspNetCore.Components.Testing`. Those packages retain the platform version prefix while keeping their own maturity label:

```text
11.0.0-preview.7.
```

Update the Device Bound Sessions package to follow the same pattern:

- Use the current ASP.NET Core platform version prefix.
- Continue producing `preview` packages when the rest of the release moves to RC or RTM.
- Do not use the platform's `rc` or stable label until the package itself is ready for that maturity level.

This avoids the hybrid `0..0-` scheme and makes DBSC consistent with the other prerelease packages shipped from this repository.

The existing `PreviewOnlyPackagePreReleaseVersionLabel`, `PreviewOnlyPackagePreReleaseVersionIteration`, and `SuppressFinalPackageVersion` mechanism should provide the intended behavior.

Locate the Device Bound Sessions package version configuration and inspect how PreviewOnlyPackagePreReleaseVersionLabel, PreviewOnlyPackagePreReleaseVersionIteration, and SuppressFinalPackageVersion are used by the other named prerelease packages. Compare the generated versioning behavior, then verify that DBSC keeps the platform version prefix and remains preview-only through RC and RTM.

Written by the indexing model from the issue text.