[UI BUG] Resource limits for type 15 (ObjectStorage) and 16 (GPU) do not sync/display correctly in Web UI

### problem

Hi,

I found that more resource limits are shown in the application then is actually mentioned in https://cloudstack.apache.org/api/apidocs-4.22/apis/updateResourceLimit.html. So I asked my AI assistent. He/she came up with additional resource type ids 12, 13, 14, 15 and 16. This seemed to work fine, except that it does not work for resource type id 15 and 16, based on that my newly imposed limits were not shown in the application. But then I tried the listResourceLimit api endpoint, and the values for both resource types (15, 16) were shown correctly. So this is about the presentation of this data in the UI.
The following problem description is created by the AI assistent. But I hope the picture is clear already.

Kind regards, Maurice.

There is a synchronization and presentation discrepancy between the CloudStack backend API and the Vue.js Web UI regarding resource limits for newer resource types (specifically resourcetype 15 for ObjectStorage and 16 for GPU).
While the backend correctly processes these values via updateResourceLimit and returns them accurately via listResourceLimits, the Web UI limits configuration panel fails to parse, map, or visually reflect these values accurately.
Steps to Reproduce
1. Update the GPU resource limit for a domain/account via the API using: updateResourceLimit resourcetype=16 max=2 ...
2. Verify the backend successfully registered the limit by calling the listResourceLimits API endpoint (the value shows up correctly).
3. Log into the CloudStack Web UI as a Root Admin and navigate to the limits configuration for that same domain/account.
4. Observe that the values for "Max. Object Storage (GiB)" and/or "Max. GPUs" do not reflect the values set via the API, or fail to display the updated state.
Expected Behavior
The Web UI's frontend mapping array should dynamically parse or correctly hardcode mappings for sequential backend resource IDs beyond 11 (including 12 through 16) so that administrative changes made via the API align 1:1 with the graphical dashboard views.
Actual Behavior
The backend successfully enforces and reports the limits via API, but the Web UI component fails to map the frontend input fields to resourcetype 15 and 16 data payloads.

### versions

The versions of ACS, hypervisors, storage, network etc..

### The steps to reproduce the bug

1.
2.
3.
...

### What to do about it?

_No response_

先定位 Vue.js 的限制設定面板及其前端資源類型對映，然後將其對資源 ID 15 和 16 的處理方式與 listResourceLimits API 回應進行比較。當 Object Storage 和 GPU 限制欄位顯示透過 updateResourceLimit 設定的值時，即表示完成；執行相關的 UI 檢查，或重現 API 和 Web UI 步驟以驗證結果。

由索引模型根據 Issue 內容生成。