Apply removeSensitiveData()'s formatted return in services()

[Terrence721]

Summary

Found via a fresh /code-review pass on app/Http/Controllers/Api/ServicesController.php (issue #70).

services() reassigned the foreach loop variable instead of writing the result back into the $services collection:

foreach ($services as $service) {
    $service = $this->removeSensitiveData($service);
}
return response()->json($services->flatten());

Sensitive fields still ended up hidden only because makeHidden() mutates the underlying model in place, but serializeApiResponse()'s key-sort/field-reordering (created_at/updated_at moved to the end, id/uuid/description/name prepended in that order) was discarded - the list endpoint's response shape was inconsistent with every other endpoint in this controller.

Fix

->map() instead of a foreach that discards its result, so removeSensitiveData()'s actual return value is what gets serialized.

Verification

TDD-proved: formats the list endpoint response the same way removeSensitiveData() formats every other endpoint asserts updated_at is the last response key (serializeApiResponse()'s guarantee - raw model attribute order does neither the alphabetical sort nor the timestamp-to-end move). Confirmed failing against the pre-fix code (databases last instead) and passing after. Full tests/v4/Feature/Api/ suite passes (236 tests). Pint/PHPStan clean on the changed file.