client: Restore spinner even when the event has been cancelled

The aborting short circuit has been introduced in 28d27f3

It can happen that the request is cancelled by another request but the second request
will use `setLoadingState` instead of `setMoreLoadingState` so `moreLoadingState` will be stuck on `LOADING`.

Not sure if it this cannot introduce a race if the same state is used in both requests.

Tried testing with {let a = new AbortController(); let f = fetch('wait.php?seconds=3', {signal: a.signal}); f.then(r => console.log(r, a)); setTimeout(() => {a.abort(); f.then((r) => console.log(r, a.signal))}, 100);}

client/js/templates/EntriesPage.jsx

@@ -111,13 +111,13 @@ function reloadList({
 
         setLoadingState(LoadingState.LOADING);
         return reloader(fetchParams, abortController).then(({ entries, hasMore }) => {
+            setLoadingState(LoadingState.SUCCESS);
+            selfoss.entriesPage.setHasMore(hasMore);
+
             if (abortController.signal.aborted) {
                 return;
             }
 
-            setLoadingState(LoadingState.SUCCESS);
-            selfoss.entriesPage.setHasMore(hasMore);
-
             if (append) {
                 selfoss.entriesPage.appendEntries(entries);
             } else {