meta-iotedge: revert aziot-edged and iotedge to 1.5.21

[rilnicki]

IoT Edge 1.5.35 only updates container images. The daemon components (aziot-edged and iotedge) remain at version 1.5.21 per upstream product-versions.json and release notes.

https://github.com/Azure/azure-iotedge/blob/1.5.35/product-versions.json

"components": [
  {
    "name": "aziot-edge",
    "version": "1.5.21"
  },
  {
    "name": "aziot-identity-service",
    "version": "1.5.6"
  },
  {
    "name": "azureiotedge-agent",
    "type": "dockerImage",
    "branch": "main",
    "repo": "Azure/iotedge",
    "version": "1.5.35"
  },
  {
    "name": "azureiotedge-hub",
    "branch": "main",
    "repo": "Azure/iotedge",
    "type": "dockerImage",
    "version": "1.5.35"
  },
  {
    "name": "azureiotedge-simulated-temperature-sensor",
    "branch": "main",
    "repo": "Azure/iotedge",
    "type": "dockerImage",
    "version": "1.5.35"
  },
  {
    "name": "azureiotedge-diagnostics",
    "branch": "main",
    "repo": "Azure/iotedge",
    "type": "dockerImage",
    "version": "1.5.21"
  }
]

The 1.5.35 daemon recipes cause runtime failures due to attempts to pull non-existent images such as: mcr.microsoft.com/azureiotedge-diagnostics:1.5.35

× configuration has correct URIs for daemon mgmt endpoint - Error
     Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.5.35' locally
     docker: Error response from daemon: manifest for mcr.microsoft.com/azureiotedge-diagnostics:1.5.35 not found: manifest unknown: manifest tagged by "1.5.35" is not found.

This change reverts the daemon recipe versions back to 1.5.21 and aligns meta-iotedge with the official Azure IoT Edge 1.5.35 version matrix.

[rilnicki]

@microsoft-github-policy-service agree company="Welotec"

[jlian]

Thanks for catching this! We will also need to update our automation accordingly. Looks like a small change. Have you tested this recipe on your side as well?

[rilnicki]

Yes, I build an image with these changes and connected to IoT Hub using a primary connection string.

[jlian]

Thanks for catching this @rilnicki. The root cause is that update-recipes.sh was using the release tag (1.5.35) for recipe versioning instead of the daemon binary version (1.5.21) from product-versions.json. Release 1.5.35 only updates Docker images while the daemon stays at 1.5.21, so the built binaries end up referencing container image tags that do not exist.

This manual fix is correct and unblocks the release. I have also added the automation fix to #196 so that update-recipes.sh and the watch/CI workflows handle this correctly going forward.

Approving -- let us merge this to unblock the release and land the automation fix via #196 separately.

[jlian]

LGTM. Correct fix for the daemon version mismatch.

[jlian]

Re-tagged and re-released 1.5.35 at the new main HEAD (with this fix included). The old tag pointed to recipes with VERSION = "1.5.35" which caused the diagnostics image pull failure.

The tag stays 1.5.35 (not 1.5.21) because it matches the upstream Azure IoT Edge release version. The recipe filenames and VERSION correctly use 1.5.21 (the daemon binary version), while the tag represents which upstream release these recipes correspond to. Updated the release notes with a version table and a note about the retag.