Docker Hub API changes may break Extension updates (in future)

Docker Hub changed their API (per docker/hub-feedback/issues/2484), which removes the current access pathway to the image architecture information. I believe we will[^1] just need to authenticate to fix this one (which is at least possible in a centralised way, unlike with [core updates](https://github.com/bluerobotics/BlueOS/issues/3489)), but in the meantime we have a broken manifest and the CI system will continue to break it (generating it with no images).

Initially raised in [this forum post](https://discuss.bluerobotics.com/t/cant-install-or-update-any-extensions-on-blueboat/21319).

[^1]: once Docker Hub add the info back to the authenticated version of the API, which they have [already said they'll do](https://github.com/docker/hub-feedback/issues/2484#issuecomment-3175459287)

まず、manifest-generation path と、イメージのアーキテクチャ情報を取得するために Docker Hub に問い合わせる CI system を追跡します。認証済み API の動作を理解するため、Docker Hub issue 2484 とリンク先の forum report を確認します。生成された manifest に期待されるイメージが含まれ、Docker Hub の access pathway が変更されても CI check が失敗しなくなれば完了です。

索引モデルが issue の本文から書いたものです。