`logging log-group list` returns nothing with `--compartmentidinsubtree true`

oci --debug logging log-group list --compartment-id $TF_VAR_tenancy_ocid --compartmentidinsubtree true using tenancy ID for compartment-id returns empty result. Log groups do exist and are returned when specifying certain Compartment IDs

% oci logging log-group list --compartment-id ocid1.tenancy.oc2..aaaaa4szcbbrkxtwhh4abenvl7yfde2d7v5vtsaaatlpjclpzhteqy3ba72a --compartmentidinsubtree true
% oci logging log-group list --compartment-id ocid1.compartment.oc2..aaaaaaaacfnkuvtrj3rm5cqulrepfpkz733japr5iimkqfc6nmwe5aiwca6a
{
  "data": [
    {
      "compartment-id": "ocid1.compartment.oc2..aaaaaaaacfnkuvtrj3rm5cqulrepfpkz733japr5iimkqfc6nmwe5aiwca6a",
      "defined-tags": {
        "Oracle-Tags": {
          "CreatedBy": "default/jeliker@mythics.com",
          "CreatedOn": "2024-07-12T17:16:19.684Z"
        }
      },
      "description": "Logging for Network resources and services",
      "display-name": "Network",
      "freeform-tags": {},
      "id": "ocid1.loggroup.oc2.us-langley-1.amaaaao6a3v47f5owdk7lz4baapxbh3nngrqvaajfhz6gg23el7vhzrum5gq",
      "lifecycle-state": "ACTIVE",
      "time-created": "2024-07-12T17:16:19.775000+00:00",
      "time-last-modified": "2024-10-17T13:26:08.027000+00:00"
    }
  ]
}

Start by reproducing the oci logging log-group list command with a tenancy OCID and --compartmentidinsubtree true, then compare it with the compartment-specific invocation shown in the issue. Trace the logging log-group list entry point and verify that the completed behavior returns existing log groups from descendant compartments when the tenancy is used.