Update Scan store to ingest `GovernanceLock`s and `VestingLock`s

Problem

ScanStore.contractFilter defines the types of contracts that will be ingested into the store, and does not currently include GovernanceLock or VestingLock.

Acceptance Criteria

Passing tests in ScanStoreTest that prove that lock contracts are ingested into the store.

Budget

0.5 days

Solution

Update contractFilter to add mkFilter calls for GovernanceLock and VestingLock similar to how it handles AmuletTransferInstruction

Risk Mitigation

• Expiry: VestingLocks use their endTime for expiry, while GovernanceLocks have no expiry time; ensures we avoid early pruning
• DSO scoping: Changes must filter contracts by DSO for proper scoping

Exclusions

• DAR bump and DarResources regeneration, though note that CI won’t pass without this
• Serving contracts over HTTP or integration tests – see #7125