Add .NET NuGet action to list of cacheable package managers

content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md

@@ -30,6 +30,7 @@
 | Gradle, Maven | [setup-java](https://github.com/actions/setup-java#caching-packages-dependencies) |
 | RubyGems | [setup-ruby](https://github.com/ruby/setup-ruby#caching-bundle-install-automatically) |
 | Go `go.sum` | [setup-go](https://github.com/actions/setup-go#caching-dependency-files-and-build-outputs) |
+| .NET NuGet | [setup-dotnet](https://github.com/actions/setup-dotnet?tab=readme-ov-file#caching-nuget-packages) |
 
 {% warning %}
 
@@ -258,7 +259,7 @@
 
 {% data variables.product.prodname_dotcom %} will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited{% ifversion actions-cache-policy-apis %}. By default, the limit is 10 GB per repository, but this limit might be different depending on policies set by your enterprise owners or repository administrators.{% else %} to 10 GB.{% endif %} {% data reusables.actions.cache-eviction-policy %}
 
 {% data reusables.actions.cache-eviction-process %} {% ifversion actions-cache-ui %}The cache eviction process may cause cache thrashing, where caches are created and deleted at a high frequency. To reduce this, you can review the caches for a repository and take corrective steps, such as removing caching from specific workflows. For more information, see "[Managing caches](#managing-caches)."{% endif %}{% ifversion actions-cache-admin-ui %} You can also increase the cache size limit for a repository. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-cache-storage-for-a-repository)."
 
 {% elsif actions-cache-policy-apis %}
 
@@ -266,11 +267,11 @@
 
 {% endif %}
 
 {% ifversion actions-cache-management %}
 
 ## Managing caches
 
 {% ifversion actions-cache-ui %}
 
 To manage caches created from your workflows, you can:
 
@@ -293,13 +294,13 @@
 
 {% else %}
 
 You can use the {% data variables.product.product_name %} REST API to manage your caches. {% ifversion actions-cache-list-delete-apis %}You can use the API to list and delete cache entries, and see your cache usage.{% elsif actions-cache-management %}At present, you can use the API to see your cache usage, with more functionality expected in future updates.{% endif %} For more information, see "[AUTOTITLE](/rest/actions/cache)."
 
 You can also install a {% data variables.product.prodname_cli %} extension to manage your caches from the command line. For more information about the extension, see [the extension documentation](https://github.com/actions/gh-actions-cache#readme). For more information about {% data variables.product.prodname_cli %} extensions, see "[AUTOTITLE](/github-cli/github-cli/using-github-cli-extensions)."
 
 {% endif %}
 
 {% ifversion actions-cache-ui %}
 
 ### Viewing cache entries
 
@@ -330,7 +331,7 @@
 
 {% endif %}
 
 {% ifversion actions-cache-list-delete-apis %}
 
 ### Force deleting cache entries