[API] Internal DB IDs used as parameters

##### ISSUE TYPE
* Improvement Request

##### COMPONENT NAME
~~~
API
~~~

##### CLOUDSTACK VERSION
~~~
Any
~~~

##### CONFIGURATION
N/A

##### OS / ENVIRONMENT
N/A

##### SUMMARY
The API accepts internal database IDs as well as UUIDs on the UUID parameters. For example:

````
(nvs) 🐱 > list accounts id=c3d932e5-488c-11ef-a188-3e7340e5df3c filter=id,name
{
"account": [
{
"id": "c3d932e5-488c-11ef-a188-3e7340e5df3c",
"name": "nicolas"
}
],
"count": 1
}
(nvs) 🐱 > list accounts id=2 filter=id,name
{
"account": [
{
"id": "c3d932e5-488c-11ef-a188-3e7340e5df3c",
"name": "nicolas"
}
],
"count": 1
}
(nvs) 🐱 > list accounts id=3 filter=id,name
{
"account": [
{
"id": "eef0d0a3-8013-4c37-954d-eafb96716c95",
"name": "baremetal-system-account"
}
],
"count": 1
}
````

##### EXPECTED RESULTS
~~~
ERROR - only UUIDs must be accepted
~~~

##### ACTUAL RESULTS
~~~
Successful API response
~~~

首先复现文档中记录的 list accounts 调用，将 id 分别设置为 UUID、2 和 3，然后跟踪 UUID 参数的 API 参数验证和查找路径。当数值型内部数据库 ID 被报错拒绝，而有效的 UUID 仍然返回 account 时，即视为完成。

由索引模型根据 Issue 内容生成。