Project search does not match the Version field

### Current Behavior

On the Projects page (`/projects`), searching using the search box does not match against the project's **Version** field. Only the project **name** appears to be searched.

Example:
- A project exists with version `5.3` (confirmed visible in the Version column when browsing/sorting).
- Typing `5.3` into the search box returns **"No matching records found"**.
- Sorting by the Version column confirms the project is present in the portfolio.

### Steps to Reproduce

1. Create/have multiple projects with different versions (e.g. same project name, multiple versions).
2. Go to the Projects page.
3. Type an existing version string into the search box.
4. Observe "No matching records found" even though a project with that version exists.

### Expected Behavior

Searching for a version string (e.g. `5.3`) should return projects whose `version` field matches, similar to how project name search already works. This is the same category of gap that was previously fixed for the `group` field in #3749.

### Dependency-Track Version

4.x

### Browser

Google Chrome

### Checklist

- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/main/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported

Start at the Projects page (`/projects`) search implementation and compare it with the earlier `group`-field fix in issue #3749. Ensure searches for an existing project version such as `5.3` return the matching project, then verify the reported reproduction steps.

Written by the indexing model from the issue text.