getSettings rebuilt the response into a hand-written map and left both feature
flags out, so SettingEntity always read null. Everything gated on them stayed
off no matter what the backend said:
- "Mostrar tarifa" in the professional profile could not be switched on
- "Servicio a domicilio" never rendered, and touching the on-site switch forced
location to office, losing both/delivery
- the patient never saw the home-vs-office dialog, so every appointment was
created as office with the professional's address
- every appointment was created with rate 0
The web reads the response as-is and never had this. Note the backend does not
ship a `tarifas` key at all yet, so rates stay off until it is added to
settings.global — this fix only stops the app from discarding it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>