Integrate OAM concepts with IDE and Dashboard

[lyzhang1999]

Currently, the KubeVela integration with Nocalhost can be done via the nocalhost trait. Here is a live demo.

Problem with IDE

But after the KubeVela app is deployed, its structure looks like following in IDE:

To make the integration more KubeVela native, we should expose OAM concepts to users, e.g. Component/Trait.

Problem with Dashboard

The dashboard will display the application deployments. But it doesn't support OAM-type application:

To make the integration more KubeVela native, we can add a OAM type.

proposal from @hongchaodeng

[FogDong]

After deploying a KubeVela Application with nocalhost trait, we can see the application under the namespace, which is awesome!

But under the application, we still have the regular workloads like deployment, maybe we can list component and trait if it's a KubeVela Application.

WDYT? @lyzhang1999

[lyzhang1999]

I think it's a good idea, Also the specific grouping information(component, trait) is only displayed when the application is of type KubeVela, which you mentioned is very important.