akri-dev uses agent image tag latest-dev, which is not up-to-date

[krumware]

Describe the bug

In the documentation, it appears that a user can use the akri-dev helm chart to use the latest development images. This may be misleading, as it appears to tag latest-dev by default if a version is not specified.

the image tag latest-dev has the following info:

        "Id": "sha256:e52023876dfdd2812e1f3e109c71072f6d2347c6f3f8eba7e8e8f919a7eba825",
        "RepoTags": [
            "ghcr.io/project-akri/akri/agent:latest-dev"
        ],
        "RepoDigests": [
            "ghcr.io/project-akri/akri/agent@sha256:49fac551124affa0af2432f21d99e5e6273c331953977620d8cd534b64774ee4"
        ],
        "Parent": "",
        "Comment": "buildkit.dockerfile.v0",
        "Created": "2023-10-19T17:48:26.562953842Z",
        "DockerVersion": "",
        "Author": "",

meanwhile latest has the following:

        "Id": "sha256:3457ca149486d4142c59675fd1d0e432b22ca663e4c85f3d4dec112bed26f225",
        "RepoTags": [
            "ghcr.io/project-akri/akri/agent:latest"
        ],
        "RepoDigests": [
            "ghcr.io/project-akri/akri/agent@sha256:4554f7ce1cbf453834e79838459f4f7d7036bb70cedad3bd5427eed21c585d3d"
        ],
        "Parent": "",
        "Comment": "buildkit.dockerfile.v0",
        "Created": "2024-11-20T22:21:49.776995468Z",
        "DockerVersion": "",
        "Author": "",

Output of kubectl get pods,akrii,akric -o wide

Kubernetes Version: [e.g. Native Kubernetes 1.19, MicroK8s 1.19, Minikube 1.19, K3s]

To Reproduce
Steps to reproduce the behavior:

1. Create cluster using '...'
2. Install Akri with the Helm command '...'
3. '...'

Expected behavior

akri-dev would use the latest dev images by default, without having to specify image version.
the latest dev release would also be tagged as latest-dev

Logs (please share snips of applicable logs)

Additional context

I found this when the akri-agent failed to launch, and reference issues were very old and have likely since been fixed.

akri.sh Agent start
akri.sh KUBERNETES_PORT found ... env_logger::init
[2025-05-02T11:26:52Z TRACE agent] akri.sh KUBERNETES_PORT found ... env_logger::init finished
[2025-05-02T11:26:52Z INFO  akri_shared::akri::metrics] starting metrics server on port 8080 at /metrics
[2025-05-02T11:26:52Z INFO  agent::util::registration] internal_run_registration_server - entered
[2025-05-02T11:26:52Z TRACE agent::util::registration] internal_run_registration_server - registration server listening on socket /var/lib/akri/agent-registration.sock
[2025-05-02T11:26:52Z TRACE agent::util::slot_reconciliation] periodic_slot_reconciliation - start
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: NotPresent', agent/src/util/slot_reconciliation.rs:336:57
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[2025-05-02T11:26:52Z INFO  agent::util::config_action] do_config_watch - enter
Error: JoinError::Panic(Id(4), ...)