"Failed to configure image with the fleet provided." using latest image

[TodorKatsarski]

Describe the bug
I'm trying to run a Balena virtual device locally and to register in Balena Cloud, however I see a warning message when I run the image and my device is not visible in my fleet in Balena Cloud. This is the message I see when I run the image:

This version of the balena CLI (15.0.3) has expired: please upgrade.
369 days have passed since the release of CLI version 16.0.0.
See deprecation policy at: https://git.io/JRHUW#deprecation-policy

The --unsupported flag may be used to bypass this deprecation check and
continue using this version of the CLI. However, note that the balenaCloud
or openBalena backends may be updated in a way that is no longer compatible
with this CLI version.

Failed to configure image with the fleet provided.

To Reproduce
Steps to reproduce the behavior:

1. Run

docker run -it \
    --restart always \
    -v bv_pid:/app/pid \
    --device=/dev/kvm \
    --cap-add=net_admin \
    --network host \
	-e API_TOKEN="" \
	-e FLEET="" \
	-e AZURE_DEVOPS_ACCESSTOKEN="" \
	-e BALENARC_BALENA_URL="balena-cloud.com" \
    ghcr.io/balena-labs-research/balena-virt:latest

Expected behavior
Device is visible in my fleet in Balena cloud.

Device Type: Local machine used for development.

[TodorKatsarski]

The cause of the issue seems to be the old Balena CLI version. The PR fixes this issue and after the fix I'm able to see my device in Balena cloud without warning messages.

[benclerix-cegeka]

+1