When we fail to retrieve service messages, we should display a toast instead of a service message banner with an error message inside

### Package / App

Other

### Description

The way service messages is being implemented now, we display a service message banner with an error message inside every time we fail to fetch service messages. When we have implemented a toast system, this should be changed to trigger a toast instead.

### Alternatives

_No response_

### Other info

_No response_

Start by locating the service-message fetch failure path and the toast-system entry point. Confirm how failures currently become banner messages and identify the toast API once available. Done means fetch failures trigger a toast rather than rendering an error inside the service-message banner.

Written by the indexing model from the issue text.