Enhancement: switch to type-lens

Nobody has claimed this yet.

### Summary

We have a lot of utility functions to help us figure out the various types from models and extract information from them. A lot of this is now included in [type-lens](https://github.com/litestar-org/type-lens), so we should be switching to using that instead.

cc: @peterschutt

### Basic Example

_No response_

### Drawbacks and Impact

I'm not sure if there's an easy way to do this without making breaking changes. There may be, but I am inclined to make the breaking changes regadlless. I don't *think* it would effect users too much since most likely it would only change things like `FieldModel` and some other stuff that polyfactory which, while technically public API, are probably not used by many users.

### Unresolved questions

_No response_

Start by locating the utility functions that inspect model types and the FieldModel code mentioned in the issue, then compare their responsibilities with type-lens. Determine the migration scope and any public API or breaking-change implications. Done means the relevant type handling uses type-lens consistently and the affected behavior remains covered by the project's existing checks.

Written by the indexing model from the issue text.