prevent duplicate updateAllUnprocessedInputs call

TimelineContext loadTimelineEntries retrieves the pipeline range, calls updateAllUnprocessedInputs for that range, and then sets the pipeline range as state via setPipelineRange.
Then in LabelTab, we have a useEffect: when pipelineRange changes, we call updateAllUnprocessedInputs (again!)
setPipelineRange is not called from anywhere else, meaning that this duplicate scenario is the time this useEffect gets called. We can remove it.

tested recording new labels, refreshing the page, and changing to different dates, and labels still get matched properly

Author: JGreenlee

www/js/TimelineContext.ts

@@ -139,6 +139,7 @@ export const useTimelineContext = (): ContextProps => {
   }, [timelineMap]);
 
   async function loadTimelineEntries() {
+    logDebug('Timeline: loadTimelineEntries called');
     try {
       const pipelineRange = await getPipelineRangeTs();
       await updateAllUnprocessedInputs(pipelineRange, appConfig);

www/js/diary/LabelTab.tsx

@@ -97,13 +97,6 @@ const LabelTab = () => {
     setDisplayedEntries(entriesToDisplay);
   }, [timelineMap, filterInputs, timelineLabelMap, filterRefreshTs]);
 
-  // once pipelineRange is set, update all unprocessed inputs
-  useEffect(() => {
-    if (pipelineRange && pipelineRange.end_ts) {
-      updateAllUnprocessedInputs(pipelineRange, appConfig);
-    }
-  }, [pipelineRange]);
-
   const Tab = createStackNavigator();
 
   const contextVals: LabelContextProps = {

www/js/diary/timelineHelper.ts

@@ -170,6 +170,7 @@ export async function updateAllUnprocessedInputs(
   pipelineRange: TimestampRange,
   appConfig: DeploymentConfig,
 ) {
+  logDebug(`timelineHelper: updateAllUnprocessedInputs for ${JSON.stringify(pipelineRange)}`);
   const tq = getUnprocessedInputQuery(pipelineRange);
   const getMethod = window['cordova'].plugins.BEMUserCache.getMessagesForInterval;
   const labelsPromises = keysForLabelInputs(appConfig).map((key) =>