Add Claw.Spec.AgentFiles to seed files stored outside of the CR

[xcoulon]

The upstream operator has spec.workspace.files for seeding individual files into the agent workspace, but enterprise deployments need to seed entire directory trees — agent configuration files (SOUL.md, AGENTS.md, TOOLS.md), project scaffolds, and shared templates. These trees live in Git repositories or ConfigMap archives and need to be injected at pod start time with control over overwrite behavior and file protection.

Without spec.agentFiles, administrators must either embed large file trees inline in the CR (impractical), build custom init containers (unsupported), or manually copy files into PVCs (doesn't scale). The existing spec.workspace.files is designed for small, individual files — not for the "seed an entire agent profile from a Git repo" use case that enterprise onboarding requires.

see https://github.com/redhat-et/claw-operator/tree/main/openspec/changes/add-agent-files

[alexeykazakov]

I think we need to extend spec.workspace.files so it supports:

1. inline file content (as it works now)
2. references to ConfigMaps
3. references to Git
4. Maybe something else? (can be added later)

It should NOT be limited to saul.md, agents.md, bootstrap.md, etc, but also suport skills and maybe other workspace files. This is why I would keep it under spec.workspace instead of introducing agentFiles.

[xcoulon]

see #222 (draft)