fix(handleMemberUpdated): consider both pinned and archived channels (#…

…2638)

### 🎯 Goal

This PR solves an issue where if `pinned_at` is missing from the `sort`,
the archived channels are not being handled properly during application
runtime.

src/components/ChannelList/hooks/useChannelListShape.ts

@@ -285,6 +285,11 @@ export const useChannelListShapeDefaults = <SCG extends ExtendableGenerics>() =>
       const considerPinnedChannels = shouldConsiderPinnedChannels(sort);
       const considerArchivedChannels = shouldConsiderArchivedChannels(filters);
 
+      // `pinned_at` nor `archived` properties are set or channel list order is locked, return early
+      if ((!considerPinnedChannels && !considerArchivedChannels) || lockChannelOrder) {
+        return;
+      }
+
       const pinnedAtSort = extractSortValue({ atIndex: 0, sort, targetKey: 'pinned_at' });
 
       setChannels((currentChannels) => {
@@ -296,9 +301,6 @@ export const useChannelListShapeDefaults = <SCG extends ExtendableGenerics>() =>
         const isTargetChannelArchived = isChannelArchived(targetChannel);
         const isTargetChannelPinned = isChannelPinned(targetChannel);
 
-        // handle pinning
-        if (!considerPinnedChannels || lockChannelOrder) return currentChannels;
-
         const newChannels = [...currentChannels];
 
         if (targetChannelExistsWithinList) {