Fix: artifacts when changing ride type as client or using the in-game console

[Broxzier]

Something I recently noticed while playing in multiplayer. When changing a ride's type while the arbitrary ride type changes is enabled, the screen only gets invalidated properly when done from the dropdown menu as the server. When running the command rides set type or changing a ride's type as a client, the screen does not invalidate, and you're left with something like this:

This part in the code makes it work properly for single-player and clients (Ride.cpp from the UI project):

OpenRCT2/src/openrct2-ui/windows/Ride.cpp

Lines 2434 to 2438 in 0da35a5

	if (rideType < RIDE_TYPE_COUNT)
	{
	set_operating_setting(w->number, RideSetSetting::RideType, rideType);
	}
	window_invalidate_all();

This PR basically moves the invalidation to the game action itself. This is outside the UI project though, but I'm not sure if there's a better way to handle screen invalidation reliably at the moment. Ideally the drawing engine should go over the game actions to see what needs to be invalidated instead.

[ZehMatt]

A lot of game actions currently use gfx_invalidate_screen, so I think this will do right now