Restore EXCLUDED CODE marker lost during the linter-merge rebase conflict

The rebase onto master (after #16's linter merge) resolved a conflict
in the commented-out cat_tools schema-restriction block by keeping a
plain /* instead of master's /* EXCLUDED CODE: ... -- without it, the
linter demands " * " prefixes on every line of the commented-out DO
block, producing 15 false findings. make lint is clean again.

Co-Authored-By: Claude <noreply@anthropic.com>

Author: jnasbyupgrade

sql/object_reference.sql

@@ -12,7 +12,7 @@
  */
 SET LOCAL client_min_messages = WARNING;
 
-/*
+/* EXCLUDED CODE: schema-restriction check below not currently enforced
 DO $$
 DECLARE
   c_schema CONSTANT name := (SELECT extnamespace::regnamespace::text FROM pg_extension WHERE extname = 'cat_tools');