Add NuGet and .NET tools caching to CI workflows

[Copilot]

Adds GitHub Actions caching for NuGet packages and .NET tools to reduce CI build times.

Changes

Cache Configuration

• NuGet packages: ~/.nuget/packages
  • Key: {OS}-nuget-{hash(*.csproj, *.sln)}
• .NET tools: ~/.dotnet/tools
  • Key: {OS}-dotnet-tools-{hash(*.csproj, *.sln)}
• Restore keys use OS-only prefix for partial cache hits across branches

Workflows Updated

• dotnet.yml: Added caching to build, security-scan, and code-quality jobs
• deploy.yml: Added caching to deploy job

Example

- name: Cache NuGet packages
  uses: actions/cache@v4
  with:
    path: ~/.nuget/packages
    key: ${{ runner.os }}-nuget-${{ hashFiles('**/*.csproj', '**/*.sln') }}
    restore-keys: |
      ${{ runner.os }}-nuget-

- name: Restore dependencies
  run: dotnet restore

Cache invalidates automatically when project files change. Expected restore time reduction: ~70-80% on cache hits.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Optimize CI with restore/build caching</issue_title>
<issue_description>Add actions/cache for NuGet and ~/.dotnet/tools to speed builds.

Acceptance Criteria:

• Cache keys include OS and project hash
• CI times reduced vs baseline</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Optimize CI with restore/build caching #12

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.