Support array response in the template

[pshao25]

All the customizable response in the arm template only accepts model. But there are cases whose response is array.

"200": {
  "description": "OK",
  "schema": {
    "type": "array",
    "items": {
      "$ref": "#/definitions/VirtualMachineImageResource"
    }
  }
}

However, if I write this operation like this

listPublishers is ArmProviderActionSync<
  Response = {
    @bodyRoot body: VirtualMachineImageResource[]
  }
>;

The emitted swagger doesn't have x-ms-pageable, which raises ci failure:

x-ms-pageable extension must be specified for LIST APIs.

If I write this operation like this

listPublishers is ComputeProviderActionSync<
    Response = Page<VirtualMachineImageResource>,
  >;

It's actually not correct because Page<> is not an array, which also leads to the mismatch with the existing example data.

[timotheeguerin]

how is it pageable if it just returns an array, what paging mechanism does it use?