frontend: service managers show old data after data-change/spinning-logo

> About deleting an IP and it staying there, it is a behavior we have in all frontend managers. Basically we put the component in an "updating" state when a change was made, and the next fetch will put update the data and put it in a "not-updating" state. The problem happens when a fetch initiates, a change occurs, and the fetch completes after the change but with the old data. There are multiple solutions to that and we should discuss on what is the behavior we want, blueos-wise (same behavior for all services).

_Originally posted by @rafaellehmkuhl in https://github.com/bluerobotics/BlueOS-docker/issues/797#issuecomment-1044652146_

As stated on the comment above, sometimes the data shown after a spinning-logo/updating-state is not the newest one, and don't reflect recent changes (e.g.: user added a new ethernet address but it doesn't show there after the spinning logo vanishes, but appear after some seconds, after a new fetch happens).

This behavior can/will confuse users and make them think an operation has not succeeded, when it did.