[TS PBT] Project properties and search violations with USVM

[CaelmBleidd]

Summary

• project supported property domains into USVM inputs with explicit exact, approximate, unsupported, and concrete-only capabilities
• execute supported synchronous preconditions and predicates in one symbolic state according to the [TS PBT][P0] Align and simplify property execution semantics before integration #384 contract
• distinguish reached violations, bounded searches without a reached violation, unsupported execution, property errors, timeouts, engine failures, and input-resolution failures
• preserve reached-target evidence even when candidate inputs cannot be represented, and extract supported inputs through JsConcreteValue
• cover scalar and collection projection, initial-state configuration, precondition handling, property search, and cross-backend conformance

Dependency

This PR is stacked on #386 and intentionally targets caelmbleidd/issue-384-property-contract. Merge #386 first, then rebase this branch onto main.

The USVM integration also needs a rebase and adaptation to the TS Calls interface changes from #377 before final merge.

Validation

The resulting source tree is identical to the previously validated combined head e250a3ba:

• npm test in fast-check-adapter: 55 passed
• focused USVM contract, projection, and search suite: 31 passed
• full :usvm-ts-pbt:test: 223 passed
• :usvm-ts-pbt:check and :usvm-ts-pbt:installDist: passed
• CI run 34232883514: all six jobs passed

Closes #351
Closes #352