fix: include harness Dockerfiles in deploy hash

[jstar0]

Summary

Dev-mode deploy skipping currently hashes project and harness config files, but not Dockerfiles referenced by harness specs. That can let canSkipDeploy short-circuit the deploy pipeline after a Dockerfile-only change, before the per-harness deployer hash has a chance to notice the update.

Closes #1380

Changes

This includes the referenced harness Dockerfile content in the project deploy hash, matching the lower-level harness deployer behavior.

Documentation PR

N/A

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Verification

npm test -- src/cli/operations/deploy/__tests__/change-detection.test.ts
npm test -- src/cli/operations/deploy
npm run typecheck
npm run lint
npm run format:check
npm run build

Note: npm run lint currently reports 34 warnings in pre-existing files outside this change; it reports 0 errors.

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly, or no documentation update is needed
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.