bugfix(camera): Advance scripted camera moves by elapsed logic time

[bobtista]

Fixes #3142.

rotateCamera, zoomCamera and pitchCamera convert their authored duration into a count of 33.33 ms frames, then advance one step per render frame, so a scripted camera move completes renderFps / logicFps times faster than the mission scripter intended. Network games hit this without any special setup, because FramePacer::getActualLogicTimeScaleFps() returns TheNetwork->getFrameRate() and pins the logic rate near 30 while the render rate follows the player's limit.

Now advances the three movements by the elapsed logic time instead of by one render frame, so they take the authored duration at any render frame rate. curFrame becomes a Real and accumulates milliseconds / TheW3DFrameLengthInMsec, which leaves the easing, the hold frames, and the remaining-time maths used by Set Final Zoom / Set Final Pitch working on the same quantities as before.

Measured with a "1 rotation over 2.00 seconds" move, logic time scale pinned at 30 FPS, varying only the max render FPS:

max render FPS	before	after
30	1960 ms	1967 ms
60	986 ms	1987 ms
120	525 ms	2000 ms

This mirrors the fix already applied to the fourth scripted camera movement in the same file: #1451 converted moveAlongWaypointPath to accumulate elapsed milliseconds fed by TheFramePacer->getLogicTimeStepMilliseconds(FramePacer::IgnoreFrozenTime), and rotate, zoom and pitch were left on the old frame-counting form. The call sites here now pass the same value.

W3DView lives in Core, so this covers both games.

Todo:

• Confirm the authored duration is honoured at 30, 60 and 120 render FPS
• Check a campaign cutscene that mixes a waypoint pan with a rotation