revert(assets): drop job_ids filter from GET /api/assets (#14408)

The job_ids query filter added in #13998 has no live consumer: the
frontend Generated tab kept sourcing from GET /jobs, and the cloud side
removed its equivalent filter from the shared asset spec. Carrying it on
the local server only re-introduces Core<->Cloud drift on the shared
contract, so remove it to match.

Removed: the job_ids field + validator on ListAssetsQuery, the IN(...)
clauses in list_references_page, the service/route passthrough, and the
filter-only tests.

Kept: the canonical-UUID prompt_id enforcement at job creation (also
landed in #13998). It stands on its own -- job ids are matched verbatim
by history keys, websocket correlation, and /interrupt -- and cloud
inherits it by running core for execution, so no divergence is created.

comfy_execution/jobs.py

@@ -25,10 +25,9 @@ def validate_job_id(value) -> str:
 
     Job ids must be UUIDs in the canonical lowercase hyphenated form. The id
     is stored and compared verbatim everywhere downstream — history keys,
-    websocket events, /interrupt matching, and the assets ``job_ids`` filter
-    (a String(36) column matched exactly) — so accepting another spelling
-    would either rewrite the client's id behind its back or mint a job whose
-    outputs the filter can never find. Rejecting loudly beats both.
+    websocket events, and /interrupt matching — so accepting another spelling
+    would silently rewrite the client's id and then miss every exact-match
+    lookup. Rejecting loudly beats that.
 
     Returns the id unchanged. Raises ValueError when the value is not a
     string in canonical UUID form.