Change notification settings to new API

[phylor]

There has been some changes to the notification settings API. This PR accomodates for that.

The old API returned an object, such as:

{
  data: {
    ride_notifications: ['sms']
  }
}

Now, the API returns an array of NotificationSetting:

{
  data: [
    {
      id: 'ride_notifications',
      name: 'ride_notifications',
      channels: ['sms']
    }
  ]
}

[phylor]

@tom-ioki It would be great to get your opinion on this PR. I had to hack around a bit to allow an API response to be an Array instead of a Hash. It works, but it looks hacky and it doesn't support etags when an array is returned.

[tom-ioki]

@tom-ioki It would be great to get your opinion on this PR. I had to hack around a bit to allow an API response to be an Array instead of a Hash. It works, but it looks hacky and it doesn't support etags when an array is returned.

Hey 👋
sorry for the late reply. It took me a while to understand the issue. Maybe we should have a short call?

[tom-ioki]

Looks good to me 👍

As discussed, I will create a follow up issue for this. Maybe we can move this logic into the model world and use some kind of keyword which indicates that the response will be an array of hashes or something like that.