fix: pack the dotnet new template so a tagged release publishes something

[davidnmbond]

Problem

Meraki.Cli is a dotnet new template package, but CI never produced a package. dotnet pack ran over a solution whose only project is a non-packable Worker SDK app, and Meraki.Cli.nuspec listed no files, so no .nupkg was created. On a release tag the publish job would have had nothing to push.

Changes

• package/Meraki.Cli.Template.csproj (PackageType=Template) packs content/ and carries the metadata from the old nuspec. It lives in a subfolder because a project next to the .slnx makes a bare dotnet restore fail with "more than one project or solution file". The standard CI pack step now works unchanged and produces exactly one package.
• Deleted Meraki.Cli.nuspec: superseded, and it hardcoded version 10.0.0.
• version.json 1.0 -> 10.0: nuget.org already has Meraki.Cli up to 7.0.8 (the nuspec's 10.0.0 was never published). At 1.0.x, new releases would be lower than the existing latest and never picked up by dotnet new install Meraki.Cli. Release-affecting: please confirm 10.0 is the version line you want.
• Ships Directory.Packages.props with the template: content/Meraki.Cli.csproj has no package versions of its own (central package management), so a generated project could not restore outside this repository.
• Leaves content.sln out of the package: next to the generated .csproj it made a bare dotnet build fail with MSB1011.

Verification

• From the repo root: dotnet restore, dotnet build -c Release (0 warnings, 0 errors) and dotnet pack -c Release --no-build produce exactly one package.
• Installed that package into an isolated template hive (--debug:custom-hive, so nothing touched the machine's template cache), ran dotnet new meraki -n Demo.App --apiKey=abc, confirmed the key was substituted, and dotnet build of the generated project: 0 warnings, 0 errors.
• Not exercised: the tag-triggered publish job itself (needs a real tag and the NuGet login).

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}