Places API returns 400 instead of 404 when a place isn't found #361

Describe the bug

GET, PUT and DELETE /v1/places/{id} return 400 Place resource not found. for an unknown id or another organization's place. Orders, vehicles, drivers and fleets return 404 in the same case. The lookup is scoped correctly, so nothing is exposed; only the status code is off.

PlaceController calls its local apiError(), which defaults to 400, at lines 149, 256 and 272. VehicleController passes 404 explicitly.

Impact

Clients that map 404 to "not found" treat a missing place as a bad request, and need a special case for this one resource.

Proposed fix

-            return $this->apiError('Place resource not found.');
+            return $this->apiError('Place resource not found.', 404);

at the three call sites. CustomerController.php:539 ("Account not found.") and DriverController.php:89 ("Company not found.") fall back to 400 the same way.

Why

A small change that makes not-found handling the same across resources.

Fleetbase v0.7.68 (fleetops 0.6.71).