Local package indexes

### Checklist

- [x] I have verified this is the correct repository for opening this issue.
- [x] I have verified no other issues exist related to my request.

### Is Your Feature Request Related To A Problem? Please describe.

_No response_

### Describe The Solution. Why is it needed?

A local Package Index allows Chocolatey CLI to perform package searches locally, without the need to reach out to the destination source / repository. Local searches have the obvious benefit of reduced bandwidth and increased response time, resulting in increased responsiveness in Chocolatey CLI.
 
Linux package managers such as dnf , yum , apt , pacman, use a local package index.
 
For clarity, NuGet does not use a local package index, querying the remote server each time.

### User Story

_No response_

### Additional Context

Package Indexes will support NuGet v3 repository feeds only. As the current CCR only supported NuGet v2, we need to wait until it supports v3.

### Acceptance Criteria

_No response_

### Related Issues

- https://github.com/chocolatey/choco/issues/820
- https://github.com/chocolatey/choco/issues/2165
- https://github.com/chocolatey/choco/issues/2144

Start by reading related issues #820, #2165, and #2144, then review the Chocolatey CLI areas involved in NuGet v3 repository feeds and the current CCR limitation. Define the missing acceptance criteria for a local package index, including how local searches avoid contacting the destination source and how the index is populated and used. Done means the agreed local-search behavior is implemented and verified against NuGet v3 feeds.

Written by the indexing model from the issue text.