feat(extra-natives/five): track switching

[Ehbw]

Goal of this PR

Introduce a way to register track switching. Track switching allows for a train to change the track index it is currently navigating along. Suggested by @glitchdetector

How is this PR achieving the goal

introduces REGISTER_TRACK_SWITCH and SET_TRACK_SWITCH_ACTIVE to allow for registration of a train switch and ability to enable/disable the track switch

This PR applies to the following area(s)

FiveM, Natives

Successfully tested on

A test resource showing the functionality plus invalid use cases that are accounted for
track-swapping-example.zip

Game builds: 1604, 2060, 3258, 3407

Platforms: Windows

Checklist

• Code compiles and has been tested successfully.
• Code explains itself well and/or is documented.
• My commit message explains what the changes do and what they are for.
• No extra compilation warnings are added by these changes.

Fixes issues

[TheGamerzs]

Great feature.

Using the example, when the train gets to the end track node after a switch, it warps back to the old track to the node index of:
(Not verified) OldSwitchNode - NewSwitchNode (in the example it seems: 3899 - 87)

I tested this with multiple clients:
If two clients have a different value for a switch (or not registered)
And one of the clients is standing on the train engine or carriages they will fling up in the sky, at the switch node

(Not sure if related to the native or my (VM or hardware))
I had two clients (cl2).
Client A registered the switch and created the train.
Client B (No switch registered) then was driving the train with Client A on a carriage.
Client B then began switching tracks (Unexpected behaviour), this seemed to switch fine.
Once Client B got to the end of the track and warped back (to the first issue location), my graphics stopped streaming new ~~~~assets then the issue with textures being a massive triangle then froze the VM
(Only happened when testing this)
This was my VM error.

[Ehbw]

If two clients have a different value for a switch (or not registered)
And one of the clients is standing on the train engine or carriages they will fling up in the sky, at the switch node

That's to be expected. When using this in a script you should ideally register the same value across all clients.

Client A registered the switch and created the train.
Client B (No switch registered) then was driving the train with Client A on a carriage.
Client B then began switching tracks (Unexpected behaviour), this seemed to switch fine.
Once Client B got to the end of the track and warped back (to the first issue location), my graphics stopped streaming new assets then the issue with textures being a massive triangle then froze the VM

The freezing does seem to be unrelated and tied to your VM. Although with the example I provided, the track it switches to is marked as a loop track (although it does not create an actual loop) rather then something like a ping-pong track and therefore will teleport back to node 0 (which is located close to the train tunnel in that area of the map)

[TheGamerzs]

Suggested change

	if (newTrack->m_nodeCount < newTrackNode)
	{
	fx::scripting::Warningf("natives", "REGISTER_TRACK_SWITCH: Invalid toNode was passed (%i), should be from 0 to %i\n", newTrackNode, newTrack->m_nodeCount);
	if (newTrack->m_nodeCount - 1 < newTrackNode)
	{
	fx::scripting::Warningf("natives", "REGISTER_TRACK_SWITCH: Invalid toNode was passed (%i), should be from 0 to %i\n", newTrackNode, newTrack->m_nodeCount - 1);

Stops Out Of Bounds stuff