fix(engine): activate compatible native versions

[rjckkkkk]

Summary

• reuse imported native engines when their detected version is still declared compatible by the current Catalog
• prefer an installed exact version over an active compatible version
• allow verified compatible inventory through the native deployment gate and prefer the active binary
• add regression coverage for compatible import, default ensure activation, exact-version precedence, and deployment selection

Validation

• go test ./... -count=1
• go vet ./...
• go test -race ./internal/engine ./internal/knowledge ./internal/hal ./cmd/aima -count=1
• Baiying AMD395: imported llama.cpp b9637 as compatible with Catalog b9330; default ensure planned reuse and activated the same inventory ID; deploy selected the same isolated dist binary; health and chat returned HTTP 200; status reached running/ready/healthy; process, port 18210, data directory, and temporary binary were cleaned

Test binary SHA256: 1faaeab635f1bcce033cf3e2c80e8216b5f503d5a4ae7fd0582d84bcc3e8cdad