onStarted() gets called after configuration change when the loader has been cleared

[ashughes]

I saw this was discussed a bit in #15, but I figured I'd open a new issue since it's a separate bug (assuming I understand how it's supposed to work).

Situation:

1. Call RxLoader.clear(), for example in onCompleted().
2. After an orientation change, onStarted() gets called (but no onNext() or onCompleted() because I've cleared the loader).

Issue:
I don't think onStarted() should get called on orientation change if the loader has been cleared.

To give more info on my use case, I'm storing the data separately in a retained fragment to handle orientation change, and only using the RxLoader to get the data initially, or to re-load the data when switching data sets. The reason I'm managing the data separately and not just using RxLoader for orientation changes is because the data can be manipulated by the UI, so the data emitted by the RxLoader after the orientation change is stale, and I don't want to have to re-fetch it from my database (especially since I already have the modified data).