Use vector for coords

I see no reason to use a table for coords. Saves us pointless conversions like the one on client side and allows for arithmetic operations.

[core]/es_extended/client/main.lua

@@ -360,7 +360,7 @@ if not Config.OxInventory then
 				obj = object,
 				label = label,
 				inRange = false,
-				coords = vector3(coords.x, coords.y, coords.z)
+				coords = coords
 			}
 		end
 

[core]/es_extended/server/functions.lua

@@ -472,7 +472,7 @@ if not Config.OxInventory then
 	function ESX.CreatePickup(type, name, count, label, playerId, components, tintIndex)
 		local pickupId = (Core.PickupId == 65635 and 0 or Core.PickupId + 1)
 		local xPlayer = ESX.Players[playerId]
-		local coords = xPlayer.getCoords()
+		local coords = xPlayer.getCoords(true)
 
 		Core.Pickups[pickupId] = { type = type, name = name, count = count, label = label, coords = coords }