Add skaffold configuration for local development loop

[czeslavo]

Context

We need a unified and efficient way to develop the operator locally. By introducing skaffold, we can automate the standard dev loop (modify, build, push, deploy).

This issue aims to provide a basic skaffold.yaml configuration and to adapt our manifests so they're usable with it (it should be able to deploy all operator dependencies and the operator built from local sources).

https://github.com/bkuzmic/skaffold-podman-kind is worth looking into for local registry setup for quicker image updates.

Prerequisite: #3144

Acceptance criteria

• skaffold.yaml configuration file is added to the repository
• kustomize is used for preparing manifests to be used by skaffold
• A single kind profile exists that allows running the dev loop against a local kind cluster
• It's documented how to use skaffold for local development

[scylla-operator-bot]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale