feat(cli): allow setting project name in .chainloop.yaml

[waveywaves]

Summary

Fixes #3063.

Extends .chainloop.yaml to support a project field, so chainloop attestation init can resolve the project name from config when --project is not provided.

Changes

• config.go: Added Project and Organization fields to DotChainloopConfig struct
• attestation_init.go: Extended the PreRunE config loader to populate projectName from config when the CLI flag is empty. Same precedence pattern as projectVersion: CLI flag > .chainloop.yaml > default.
• Removed MarkFlagRequired("project"): The flag is no longer required by cobra since the value can come from config. The existing deprecation warning at line 156 still fires when neither flag nor config provides a project name.

Example .chainloop.yaml

```yaml
project: my-project
projectVersion: v1.2.0
```

Note on organization

The Organization field is added to the struct for forward-compatibility, but org override is not wired up in this PR. The organization is baked into the gRPC connection credentials during PersistentPreRunE (root.go:169), before att init's PreRunE runs. Supporting org from config requires loading .chainloop.yaml earlier in the command lifecycle — left for follow-up discussion.

Test plan

• go build ./... passes
• Commits GPG-signed and DCO signed-off
• Manual test: att init with --project flag still works as before
• Manual test: att init without --project reads from .chainloop.yaml

🤖 Generated with Claude Code

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="app/cli/cmd/config.go">

<violation number="1" location="app/cli/cmd/config.go:165">
P2: Added `.chainloop` `organization` field is unused, causing a silent no-op that can mislead users.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.}

[cubic-dev-ai]

P2: Added .chainloop organization field is unused, causing a silent no-op that can mislead users.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At app/cli/cmd/config.go, line 165:

<comment>Added `.chainloop` `organization` field is unused, causing a silent no-op that can mislead users.</comment>

<file context>
@@ -161,4 +161,6 @@ func isDir(filename string) bool {
 type DotChainloopConfig struct {
 	ProjectVersion string `yaml:"projectVersion"`
+	Project        string `yaml:"project"`
+	Organization   string `yaml:"organization"`
 }
</file context>

[waveywaves]

@migmartri @jiparis Ready for review. Extends .chainloop.yaml to support a project field — same precedence pattern as projectVersion (CLI flag > config > default). Organization field left for follow-up due to gRPC connection lifecycle constraints. All commits GPG-signed.