Improve the UI/API related to site to site vpn connections

### The required feature described as a wish

As admin user currently to identify the relation between vpc, vpn connections , site to site vpn , vpn customer gateway, vpngateways is difficult from api and also from the ui prespective

It would be great we could improve the api and Ui related operations to site to site vpn

https://docs.cloudstack.apache.org/en/4.22.1.0/adminguide/networking/site_to_site_vpn.html

UI/API Issue 1: Show the associated s2svpngatewayid and s2scustomergatewayid and vpc in the vpn connections page

Navigate to Network > VPN Connections

The listVpnConnections has the s2scustomergatewayid and s2svpngatewayid in the api response and also vpcid as a parameter

https://cloudstack.apache.org/api/apidocs-4.22/apis/listVpnConnections.html

Expected behaviour

As Admin user i would like to know to which to vpn customer gateway ( name) and to which vpc (name) that a particular vpn connection is assoicated with.

Remembering the IP address and UUID is not possible

--------

UI/API Issue 2: Differnt views present when creating a vpn connection

Navigate > Network > Create VPN connection >

Navigate > Network > VPC > VPN Connection > Create Site to Site VPN Connection

Expected behaviour

Show a consistent form to avoid confusion

----

UI issue 3: Rename ( Network > Site-to-Site VPN ) to VPN gateways

Its calling the listVpnGateways api

https://cloudstack.apache.org/api/apidocs-4.22/apis/listVpnGateways.html

Expected behaviour

The site to site vpn is not a proper name

-----
UI issue 4: Show the VPC details in the main page Network > Site to Site VPN

The vpc details is visible after clicking the IP address

----
UI/Api issue 5: Show the VPC associated with VPN customer gateways

https://cloudstack.apache.org/api/apidocs-4.22/apis/listVpnCustomerGateways.html

Network > VPN Customer gateway

まず、Network > VPN Connections、Site-to-Site VPN、VPN gateways、VPN Customer gateway の各ビューを、listVpnConnections、listVpnGateways、listVpnCustomerGateways API のドキュメントと併せて確認します。2 つの VPN 接続作成フローを比較し、既存のレスポンスが VPC とゲートウェイの関連付けをどのように公開しているかを特定します。記載されたビューで関連する名前と VPC の詳細が表示され、作成フォームの一貫性が保たれていれば完了です。

索引モデルが issue の本文から書いたものです。