Add ProcessLineAgainstMesh

[Pirulax]

This PR adds a new function ProcessLineAgainstMesh, that is supposed to do a raycast against an element's renderable mesh model [not the collision model!].
The same functionality is already present in #3099, but the latter is a little buggy due to the fact that the collision model is always simplified, and not exactly the same as the mesh, and this leads to situations where no hit is detected, even though the visible mesh is hittable.
Also, when one is interested in a specific element the overhead is a lot smaller [as we can skip all the collision detection done by processLineOfSight]
The reason I didn't make it be a standalone function in the beginning is that not all game entitites can be represented as CClientEntity [For example IPL objects].

float u, float v, string textureName, string frameName, float hitX, float hitY, float hitZ = processLineAgainstMesh(Element targetElement, float startX, float startY, startZ, float endX, float endY, float endZ)

[CrosRoad95]

does it take an account animated models like 3425? i expect that when i use this function the results will match what i see. also, does it work for peds and vehicles?

[Pirulax]

No clue, haven't tried.
It does work for vehicles, and I guess it should work for peds too.
afaik animations don't affect the geometry directly, but only what is rendered, so the answer is no I believe

[Pirulax]

I've applied the requested suggestions.