libnm: fix return value for nm_remote_settings_load_connections() to ignore server result
nm_remote_settings_load_connections() and nm_remote_settings_load_connections_async() behave inconsistently. It's unexpected, that a FALSE return value may leave @Error unset. Note that before commit 22e830f0 ('settings/d-bus: fix boolean return value of "LoadConnections"'), the server boolean response would have been bogus anyway (at least for some versions). Unify the behavior, and ignore the boolean return value.
Showing with 19 additions and 11 deletions