Consolidate repo workflows by making Mise the canonical task runner

[choufraise]

Summary

This issue tracks consolidating repository workflows around a single primary task runner.

Today the repo mixes:

• Kubebuilder-style Makefile targets
• team-introduced mise.toml tooling and tasks

This creates two workflow entrypoints and increases the risk of drift between local development, CI, and documented commands.

Problem

The repository currently uses both make and mise for overlapping responsibilities:

• task execution
• tool bootstrapping
• local developer workflows

That makes it unclear which interface is canonical and increases maintenance cost when tasks, prerequisites, or version assumptions change.

Goal

Make mise the canonical workflow tool for this repository, while keeping compatibility with existing Kubebuilder expectations where needed.

Proposed direction

• move task definitions to mise.toml
• keep mise as the source of truth for local developer workflows
• reduce the Makefile to thin compatibility wrappers, or remove it later if no longer needed
• update CI and documentation to use the canonical workflow consistently

Scope

Examples of workflows to review:

• test
• lint
• manifests
• generate
• build
• run
• e2e-related tasks
• any repo-specific helper scripts

Acceptance criteria

• one clearly documented canonical workflow tool
• no duplicated task logic across Makefile and mise.toml
• CI uses the same canonical workflow definitions as local development
• contributor-facing docs are updated accordingly

Notes

Kubebuilder scaffolding currently favors make, so compatibility wrappers may still be useful even if mise becomes the primary entrypoint.