Non-matching types for IDs (int64) and query parameter requested_items (array of int32)

### Bug Description:

The entry IDs of tree entries (e.g. `XYTreeEntry` or `TimeGraphEntry`) through their base class `TreeDataModel`) are defined as int64 numbers (as well parentId). Those IDs are passed as input parameters in array `requested_items` to fetch the data (e,g, xy series, timegraph rows) for those entries, however the `requested_items` is defined as an array of int32 numbers.

The same is true for the `TooltipParameters`.

The types need to match in the API. Once this is fixed in the API the sever and client implementations need to be adapted for this.

### Steps to Reproduce:

1. Open API.yaml
2. See data structure definition for `TreeDataModel`
3. See data structure definitions for `RequestedParameters` and `GenericXYRequestedParameters` and `TooltipParameters`

### Additional Information

Note: API definition needs to be updated through swagger annotations in the Trace Compass server.

Iniziate da API.yaml e confrontate TreeDataModel e il relativo tipo parentId con requested_items in RequestedParameters, GenericXYRequestedParameters e TooltipParameters. Tracciate quindi le annotazioni Swagger nel server Trace Compass e individuate le implementazioni client e server che utilizzano questi campi. Il lavoro è completato quando i tipi dell’API corrispondono e le implementazioni interessate sono adattate in modo coerente.

Scritto dal modello di indicizzazione a partire dal testo della issue.