[Bug]: The list of capabilities for a registry is sometime empty for several registries

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Asking the list of the capabilities of the plan of a registry display an empty list:

$ ovhcloud cloud managed-registry plan list-capabilities 1f94ea45-xxxx-xxxx-xxxx-105413579fc3
┌──┬────┬─────────────┬────────────┬───────────────┐
│id│name│vulnerability│imageStorage│parallelRequest│
├──┼────┼─────────────┼────────────┼───────────────┤
└──┴────┴─────────────┴────────────┴───────────────┘
💡 Use option -o json or -o yaml to get the raw output with all information

# it's a registry in DE

# sometimes not for another registry ...

$ ovhcloud cloud managed-registry plan list-capabilities 69ed3abd-yyyy-yyyy-yyyy-a0c5de3b62b1
┌──────────────────────────────────────┬────────┬───────────────┬──────────────┬─────────────────┐
│                  id                  │  name  │ vulnerability │ imageStorage │ parallelRequest │
├──────────────────────────────────────┼────────┼───────────────┼──────────────┼─────────────────┤
│ c5ddc763-be75-48f7-b7ec-e923ca040bee │ MEDIUM │ true          │ 600G         │ 45              │
│ 0dae73df-6c49-47bf-a9d5-6b866c74ac54 │ LARGE  │ true          │ 5T           │ 90              │
└──────────────────────────────────────┴────────┴───────────────┴──────────────┴─────────────────┘
💡 Use option -o json or -o yaml to get the raw output with all information

# it's a registry in GRA

Expected Behavior

Display the list of capabilities for all the registries

Steps To Reproduce

``
$ ovhcloud cloud managed-registry plan list-capabilities 1f94ea45-xxxx-xxxx-xxxx-105413579fc3
┌──┬────┬─────────────┬────────────┬───────────────┐
│id│name│vulnerability│imageStorage│parallelRequest│
├──┼────┼─────────────┼────────────┼───────────────┤
└──┴────┴─────────────┴────────────┴───────────────┘
💡 Use option -o json or -o yaml to get the raw output with all information

$ ovhcloud cloud managed-registry plan list-capabilities 69ed3abd-yyyy-yyyy-yyyy-a0c5de3b62b1
┌──────────────────────────────────────┬────────┬───────────────┬──────────────┬─────────────────┐
│ id │ name │ vulnerability │ imageStorage │ parallelRequest │
├──────────────────────────────────────┼────────┼───────────────┼──────────────┼─────────────────┤
│ c5ddc763-be75-48f7-b7ec-e923ca040bee │ MEDIUM │ true │ 600G │ 45 │
│ 0dae73df-6c49-47bf-a9d5-6b866c74ac54 │ LARGE │ true │ 5T │ 90 │
└──────────────────────────────────────┴────────┴───────────────┴──────────────┴─────────────────┘
💡 Use option -o json or -o yaml to get the raw output with all information

### Anything else?

_No response_

Start with the cloud managed-registry plan list-capabilities command and reproduce the empty result using the DE and GRA registry examples in the issue. Trace how capabilities are fetched and displayed, then verify that the command returns the expected capabilities for registries affected by the regional behavior.