fix: allow mixed/unknown CollectionType libraries in path matching

The previous type-match guard required an exact CollectionType match
(movies or tvshows), which silently dropped notifications for libraries
with a null/undefined CollectionType and for "mixed"-type libraries
(a common setup for separate Anime / Anime Movies libraries).

Now only explicit cross-type mismatches are rejected (movie in a tvshows
library, episode in a movies library), consistent with the existing
isTypeMatch logic in api/jellyfin.js.

Author: retardgerman

jellyfinWebhook.js

@@ -827,8 +827,12 @@ export async function handleJellyfinWebhook(req, res, client, pendingRequests, o
                     const libTypeLower = lib.CollectionType?.toLowerCase();
 
                     let typeMatch = true;
-                    if (itemTypeLower === "movie" && libTypeLower !== "movies") typeMatch = false;
-                    if ((itemTypeLower === "series" || itemTypeLower === "season" || itemTypeLower === "episode") && libTypeLower !== "tvshows") typeMatch = false;
+                    if (libTypeLower) {
+                      // Only reject known cross-type mismatches; allow "mixed" and any
+                      // unrecognised CollectionType (e.g. custom anime libraries) through.
+                      if (itemTypeLower === "movie" && libTypeLower === "tvshows") typeMatch = false;
+                      if ((itemTypeLower === "series" || itemTypeLower === "season" || itemTypeLower === "episode") && libTypeLower === "movies") typeMatch = false;
+                    }
 
                     if (typeMatch) {
                       libraryId = lib.ItemId;