Run cursor action pre-draw logic before capturing the object under th…

[NayiemW]

Since the MapUI / MapView split, TechnoUnderCursor has been passed into MapView.Draw before the active cursor action’s PreMapDraw logic runs.

This breaks placement range indicators because building placement previews assign TechnoUnderCursor inside PreMapDraw. Since the renderer receives the previous value, it does not see the newly assigned object during that frame. The property is then reset during the next update cycle, so range indicators never appear while placing buildings such as pillboxes.

Previously, the relevant order was effectively:

PreMapDraw
→ read TechnoUnderCursor
→ draw map and range indicators
→ PostMapDraw

After the split, it became:

read and pass TechnoUnderCursor
→ PreMapDraw
→ draw map
→ PostMapDraw

This change moves the PreMapDraw invocation into MapUI.Draw, before TechnoUnderCursor is passed to the renderer. MapView.Draw no longer invokes it a second time.

The corrected order is therefore:

PreMapDraw
→ pass the updated TechnoUnderCursor to MapView
→ draw map and range indicators
→ PostMapDraw

PostMapDraw remains in its existing location, so the intended call order around map rendering is preserved while ensuring placement previews can display their range indicators.

[Rampastring]

Good catch. Due to conflicts I couldn't merge this PR directly, but I fixed the bug in 5c5b5f3 and added you as a co-author to the commit, while also leaving out the AI's excessive comments in MapView.cs.