fix(build): include Quota project in Debug solution builds

[iammukeshm]

Problem

#1296 added Quota.csproj to FSH.Starter.slnx, but with a Debug build exclusion:

<Project Path="BuildingBlocks/Quota/Quota.csproj">
  <Build Solution="Debug|*" Project="false" />
</Project>

In solution builds, MSBuild removes ProjectReferences to projects that are disabled in the active solution configuration. So a plain dotnet build src/FSH.Starter.slnx (Debug by default) — or F5 in Visual Studio — compiled Storage and Web without the FSH.Framework.Quota reference and failed with the exact errors reported in #1291:

Storage\Extensions.cs(5,21): error CS0234: The type or namespace name 'Quota' does not exist in the namespace 'FSH.Framework'
Storage\QuotaMeteredStorageService.cs(24,22): error CS0246: The type or namespace name 'IQuotaService' could not be found
Web\Extensions.cs(5,21): error CS0234: The type or namespace name 'Quota' does not exist in the namespace 'FSH.Framework'

Backend CI stayed green because it builds Release, where the exclusion did not apply.

Fix

Remove the build exclusion so Quota builds in every solution configuration:

<Project Path="BuildingBlocks/Quota/Quota.csproj" />

Also reverts the package-lock.json churn from the same PR ("peer": true flags injected by a different npm version, with no corresponding package.json change) so a plain npm install no longer dirties the working tree.

Verification

• dotnet build src/FSH.Starter.slnx -c Debug — 0 errors (failed with the 5 errors above before this change)
• dotnet build src/FSH.Starter.slnx -c Release — 0 errors
• Working-tree lockfiles after npm install are byte-identical to the pre-fix(solution): register missing Quota project in FSH.Starter.slnx (resolves NU1105) #1296 state

Fixes the remaining build failure in #1291.

🤖 Generated with Claude Code