Fix scan-to-compile pinning format propagation

[joakimmoller]

Summary

• propagate scan job pinning formats to compile job creation in ScannerEffector by setting overwrite_pinning_matrices from scanning_job.pinning_formats
• add regression tests that verify pinning formats are copied into the compile model and serialized into the RPC compile payload
• bump project version from 3.1.0 to 3.1.1 and update uv.lock

Why

Compile jobs created from scan flows could miss pinning format overrides, causing downstream compilation/analysis to run with unintended pinning matrices.

Changes

• update ScannerEffector setup path to include overwrite_pinning_matrices when creating compile project model
• add unit tests in tests/unit/server/test_scanning_effector.py:
  • setup copies scan pinning formats to compile model
  • compile request payload includes overwrite_pinning_matrices

Validation

• uv run pytest tests/unit/server/test_scanning_effector.py -q
• result: 2 passed

Impact

• aligns compile behavior with scan configuration
• reduces risk of incorrect pinning interpretation during analysis for non-default pinning layouts
• low risk: targeted change with direct test coverage