Always offline mutation logs printed even though internet connection exist

**There is lot of logs printing from aws appsync offline mutation.**

```
2020-02-13 20:08:56.822 12829-13080/com.hubble.care V/AppSyncOfflineMutationInterceptor: Thread:[9322]: processing Mutations
2020-02-13 20:08:56.823 12829-13080/com.hubble.care V/QueueUpdateHandler: Thread:[9322]: Got message to take action on the mutation queue.
2020-02-13 20:08:56.823 12829-13080/com.hubble.care V/QueueUpdateHandler: Thread:[9322]: Got message to process next mutation if one exists.
2020-02-13 20:08:56.824 12829-13075/com.hubble.care V/AppSyncOfflineMutationInterceptor: Thread:[9317]: processing Mutations
2020-02-13 20:08:56.825 12829-13075/com.hubble.care V/QueueUpdateHandler: Thread:[9317]: Got message to take action on the mutation queue.
2020-02-13 20:08:56.825 12829-13075/com.hubble.care V/QueueUpdateHandler: Thread:[9317]: Got message to process next mutation if one exists.
2020-02-13 20:08:56.828 12829-13075/com.hubble.care V/AppSyncOfflineMutationManager: Thread:[9317]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
2020-02-13 20:08:56.828 12829-13075/com.hubble.care V/AppSyncOfflineMutationManager: Thread:[9317]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
```

The issue names AppSyncOfflineMutationInterceptor, QueueUpdateHandler, and AppSyncOfflineMutationManager in the log output, but no source files or tests. Start by locating those log statements and tracing why they run with an internet connection. Done means the unwanted offline mutation logs no longer appear in that situation while mutation processing still works.

Written by the indexing model from the issue text.