Release v1.0.0

chore: bump remaining packages to 26.1.3.x release wave

Rebuilds/version-bumps the remaining packages not covered by the initial
26.1.3 DevExpress upgrade pass, so their published nuget.org dependency
graphs actually reference the current versions of their sibling packages:

- DX.Data.Xpo.Mapster (26.1.3.32): now depends on DX.Data.Xpo 26.1.3.36,
  picking up DevExpress v26.1.3 transitively
- DX.Data.Xpo.Identity.Mapster (26.1.3.35): now depends on
  DX.Data.Xpo.Identity 26.1.3.35 / DX.Data.Xpo.Mapster 26.1.3.32
- DX.Blazor.Identity (26.1.3.28): now depends on DX.Data.Xpo.Identity 26.1.3.35
- DX.Blazor.Identity.Server (26.1.3.26), DX.Blazor.Identity.Wasm (26.1.3.26):
  now depend on DX.Blazor.Identity 26.1.3.28

- DX.Data (26.1.3.35), DX.Data.EF (26.1.3.35), DX.Data.EF.Mapster (26.1.3.33):
  no direct or transitive DevExpress dependency, version bumped only to keep
  the whole repo in the same release wave (matches existing convention,
  e.g. DX.Utils already followed this pattern)

DX.Data.Xpo.Interfaces intentionally left untouched: it's unreferenced by
any other project in the solution and already self-declared obsolete in its
own PackageReleaseNotes.