Fix Drizzle SQLite class constructor property semantics

[andrewtdiz]

Summary:

• avoid treating constructor .prototype backrefs as the object's [[Prototype]], which lets Object.getPrototypeOf(Function.prototype) fall back correctly
• preserve INT32-tagged class constructor refs when PutValueSet writes dynamic/static properties, so class namespace patterns like SQL.Aliased stay readable and valid for instanceof
• add focused parity coverage for the constructor walk and class static property assignment paths

Closes #1024
Closes #1069

Validation:

• cargo check -p perry-runtime
• cargo build --release -p perry -p perry-runtime -p perry-stdlib
• PERRY_BIN=/root/perry-worktrees/perry-drizzle-sqlite-hang-20260605/target/release/perry PERRY_NO_AUTO_OPTIMIZE=1 npm exec --yes --package=node@26 -- bash -lc './run_parity_tests.sh --suite node-suite --module object --filter constructor-prototype-chain'
• PERRY_BIN=/root/perry-worktrees/perry-drizzle-sqlite-hang-20260605/target/release/perry tests/release/packages/_harness.sh --filter drizzle-sqlite
• cargo fmt --all -- --check
• git diff --check
• ./scripts/check_file_size.sh

Non-goal:

• dynamic new through a class constructor stored on another class remains outside this package fix; the covered contract is property read plus instanceof RHS behavior used by the Drizzle path.