fix(crafter): resolve commit info in git worktrees

[jiparis]

Summary

• Enable EnableDotGitCommonDir in go-git's PlainOpenOptions so that git worktrees can properly resolve HEAD via .git/commondir
• Previously, running chainloop att init from a worktree returned no commit info because go-git couldn't follow the commondir reference to resolve HEAD

[in a worktree ...]
./chainloop att init --workflow mywf --project myproject --replace
WRN User-attended mode detected. This is intended for local testing only. For CI/CD or automated workflows, please use an API token.
This command will run against the organization "silly-greider-943"
Please confirm to continue y/N
y
INF discovered AI agent config files agent=claude files=7
INF uploading ai-agent-config-claude-3750200425.json - sha256:6b3ef54d6edfada4b2b1e5294c8946b7842a258af960008b42d5fc591c0038e8
INF successfully collected AI agent configuration agent=claude
INF Attestation initialized! now you can check its status or add materials to it
┌───────────────────────────┬──────────────────────────────────────┐
│ Initialized At            │ 09 Apr 26 21:47 UTC                  │
├───────────────────────────┼──────────────────────────────────────┤
│ Attestation ID            │ 9cf70434-5352-492e-b12e-6a6b79c894cd │
│ Organization              │ silly-greider-943                    │
│ Name                      │ mywf                                 │
│ Project                   │ myproject                            │
│ Version                   │ v1.89.11+next (prerelease)           │
│ Contract                  │ myproject-mywf (revision 4)          │
│ Timestamp Authority       │ http://timestamp.digicert.com        │
│ Policy violation strategy │ ADVISORY                             │
│ Policies                  │ ------                               │
│                           │ source-commit: Ok                    │
└───────────────────────────┴──────────────────────────────────────┘

Closes #3018

[cubic-dev-ai]

No issues found across 2 files

[migmartri]

Is this related to this upgrade? #2966

[jiparis]

Is this related to this upgrade? #2966

Probably not. It was a missing configuration in the library.