Fix: make standalone contract templates use the local compiler tool

[Jim8y]

Summary

• add the missing local tool manifest to the NEP-11 template
• restore and invoke nccs through the local tool manifest in all standalone contract templates
• document the generated tool manifest
• validate every template manifest and compiler command

Why

The standalone templates invoked a global nccs command. A clean environment could generate a contract successfully but fail on dotnet build, and the NEP-11 template did not include a tool manifest at all.

Validation

• template unit tests: 55 passed
• packed and installed Neo.SmartContract.Template.3.10.0.nupkg
• generated a clean NEP-11 project from the package
• Release build restored the local compiler and produced the NEF and manifest with 0 errors
• targeted dotnet format --verify-no-changes

Part of #1841.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.22%. Comparing base (11bd7a1) to head (7b24709).
⚠️ Report is 4 commits behind head on master-n3.

Additional details and impacted files

@@              Coverage Diff              @@
##           master-n3    #1906      +/-   ##
=============================================
- Coverage      84.23%   84.22%   -0.01%     
=============================================
  Files            308      308              
  Lines          28229    28219      -10     
  Branches        3980     3980              
=============================================
- Hits           23778    23768      -10     
  Misses          3459     3459              
  Partials         992      992              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.