feat(persistence)!: inline vs-solutionpersistence; rename SolutionModel → Solution; namespace cleanup

[ChrisonSimtian]

⚠️ Breaking change — package IDs and namespaces change. Migration paths preserved via the Nuke.Common.ProjectModel.* transition shim.

Closes #248. Codefix follow-up tracked in #253.

Affected surface

Was	Now
Fallout.SolutionModel (package, project, assembly)	Fallout.Solution at src/Persistence/Fallout.Solution/
Fallout.VisualStudio.SolutionPersistence (package, project, assembly)	Fallout.Persistence.Solution at src/Persistence/Fallout.Persistence.Solution/
Fallout.Common.ProjectModel.* namespace	Fallout.Solutions.* (plural per BCL convention)
Microsoft.VisualStudio.SolutionPersistence.{Model,Serializer,Utilities,...} namespace	Fallout.Persistence.Solution.{Model,Serializer,Utilities,...}
vendor/vs-solutionpersistence/ submodule	gone — sources inlined
ChrisonSimtian/vs-solutionpersistence repo	now unreferenced; archive in #11 cleanup

Summary

• Vendored fork eliminated. The fork-of-fork-of-Microsoft (vendor/ submodule pointing at ChrisonSimtian/vs-solutionpersistence) is gone. 92 source files inlined into a new Fallout.Persistence.Solution project under src/Persistence/, owned outright by Fallout. No more submodule + fork-rebase coordination.
• Onion layering. src/Persistence/ is now the layered home for persistence-ring code. Future persistence-related projects go here.
• Facade renamed and rehoused. src/Fallout.SolutionModel/ → src/Persistence/Fallout.Solution/. The rebrand-era namespace mismatch (Fallout.Common.ProjectModel) is fixed to match the assembly name — Fallout.Solutions (plural to avoid Fallout.Solution.Solution awkwardness).
• Transition shim preserved. src/Shims/Nuke.Common/ShimMarker.cs now declares two mappings: the existing Fallout.Common.* → Nuke.Common.* plus a new Fallout.Solutions.* → Nuke.Common.ProjectModel.*. NUKE-era consumer code using using Nuke.Common.ProjectModel; [Solution] readonly Solution Solution; keeps compiling.

What's NOT in this PR

• Visibility narrowing. Parser types stay public for now. The [InternalsVisibleTo] decorations on Fallout.Persistence.Solution.csproj are future-intent. Per-type narrowing needs cascading CS0050 analysis — separate PR.
• Codefix update. Fallout.Migrate.Analyzers's Nuke→Fallout rewriter still produces Fallout.Common.ProjectModel.* (which is now a dead namespace). Test expectations temporarily reverted to match today's behavior. Tracked in Update Nuke→Fallout codefix to map Common.ProjectModel → Solutions for v11 #253.
• Dead-code prune. Inlined the full 92-file surface; auditing which files are actually used by Fallout's call graph is a follow-up.
• Archiving the old fork repo. Once this merges, ChrisonSimtian/vs-solutionpersistence is unreferenced. Archive (or transfer to Fallout-build once that's live) — tracked in chore(ci): drop Qodana #11.

Test plan

• dotnet build fallout.slnx — green, 0 warnings, 0 errors
• dotnet test fallout.slnx --no-build — 453 passed, 7 skipped, 0 failed across 12 assemblies
• StronglyTypedSolutionGeneratorTest.Test#Solution.g.verified.cs snapshot regenerated (reflects new project list + namespace)
• CI green on PR
• Verify a downstream NUKE-era consumer using Nuke.Common.ProjectModel.Solution still compiles against the new shim (manual / by Dennis)

[ChrisonSimtian]

Rebased onto #256 (feat/consumer-compat-tests-on-main). The rebase deliberately surfaced the breaking change — Fallout.Consumer.Local failed to compile because its using Fallout.Common.ProjectModel; and ProjectReference to src/Fallout.SolutionModel/ both stopped resolving against the renamed code. Resolved by updating the consumer csproj (new path: src/Persistence/Fallout.Solution/) and the using (new namespace: Fallout.Solutions) in the same commit. That update IS the documented consumer migration recipe.

Nuke.Consumer was unaffected (the new Fallout.Solutions.* → Nuke.Common.ProjectModel.* shim mapping covered the rename transparently).

Fallout.Consumer.NuGet was unaffected (pinned to 11.0.8 which predates the rename).

So the consumer-compat matrix correctly identified exactly which downstream pattern is affected by this PR — and the resolution is the migration path. Local + full-suite tests green.