Feat: support module-definition plugin

[mujinhuakai]

Description of your changes

support definition plugin

we can write a module-definition plugin and enabled

and then we can see it override the default module-definition properties editor form

the plugin implementation demo is to reference https://github.com/mujinhuakai/velaux-plugin-topology/tree/main

Fixes #

I have:

• Read and followed KubeVela's contribution process.
• Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
• Run yarn lint to ensure the frontend changes are ready for review.
• Run make reviewableto ensure the server changes are ready for review.
• Added backport release-x.y labels to auto-backport this PR if necessary.

Special notes for your reviewer

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: -2.01 ⚠️

Comparison is base (d2ecefa) 60.91% compared to head (6899d4c) 58.91%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #835      +/-   ##
==========================================
- Coverage   60.91%   58.91%   -2.01%     
==========================================
  Files         109      114       +5     
  Lines       19375    19819     +444     
==========================================
- Hits        11803    11676     -127     
- Misses       6104     6703     +599     
+ Partials     1468     1440      -28     

Flag	Coverage Δ
apiserver-unittests	32.15% <ø> (-1.68%)	⬇️
server-e2e-tests	48.32% <0.00%> (-0.92%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
pkg/plugin/types/plugin.go	40.00% <ø> (ø)
pkg/server/interfaces/api/assembler/v1/do2dto.go	87.30% <0.00%> (-0.34%)	⬇️
pkg/server/interfaces/api/dto/v1/types.go	73.33% <ø> (ø)

... and 29 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[chivalryq]

There's some implementation problems, but before that, can you show the screenshots for what this plugin looks like?

[chivalryq]

Seems like you are providing a framework user can continue to develop a kind of plugin, which will override the specified definition properties form?

[chivalryq]

Seems like you are providing a framework user can continue to develop a kind of plugin, which will override the specified definition properties form?

[mujinhuakai]

Seems like you are providing a framework user can continue to develop a kind of plugin, which will override the specified definition properties form?

Yes, user can write plugin to override component\trait\policy\workflow-step properties form

[chivalryq]

I have seen lot's of duplicated code of the "definition" plugin and original plugin. We can implement that by add some fields to that.
Also you can link your implementation references (Tolology Policy) to this PR.

[mujinhuakai]

I have seen lot's of duplicated code of the "definition" plugin and original plugin. We can implement that by add some fields to that. Also you can link your implementation references (Tolology Policy) to this PR.

Point 2, Do you mean commit the code of topology-policy plugin as a demo plugin ?

[chivalryq]

I have seen lot's of duplicated code of the "definition" plugin and original plugin. We can implement that by add some fields to that. Also you can link your implementation references (Tolology Policy) to this PR.

Point 2, Do you mean commit the code of topology-policy plugin as a demo plugin ?

I mean you can attach the implementation at introductio and seems you have done that.