Feat: add a built in garbage-collect policy to application

[yangsoon]

Description of your changes

add a built in garbage-collect policy, while now only support one option keepLegacyResource, which means gc mechanism will keep the legacy resource when application is updated. you can enable the keepLegacyResource options like:

apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: first-vela-app
spec:
  components:
    - name: express-server
      type: webservice
      properties:
        image: crccheck/hello-world
        port: 8000
      traits:
        - type: ingress-1-20
          properties:
            domain: testsvc.example.com
            http:
              "/": 8000
  policies:
    - name: keep-legacy-resource
      type: garbage-collect
      properties:
        keepLegacyResource: true

what will the gc mechanism do when enable the keepLegacyResource options

1. resources with the same GVK and name will be normal updated, and the OwnerReference of those resources will refer to the new resourcesTracker.
2. the expired resources and resourceTracker will be keep in cluster.
3. you can delete all resource by delete the application

TODO

• add more test

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 make reviewable to ensure this PR is ready for review.
• Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

cc @Somefive @wangyikewxgm @captainroy-hy

[codecov]

Codecov Report

Merging #2575 (9cc9273) into master (8bcffb9) will decrease coverage by 0.04%.
The diff coverage is 47.32%.

@@            Coverage Diff             @@
##           master    #2575      +/-   ##
==========================================
- Coverage   59.86%   59.81%   -0.05%     
==========================================
  Files         223      223              
  Lines       22735    22824      +89     
==========================================
+ Hits        13610    13652      +42     
- Misses       7473     7515      +42     
- Partials     1652     1657       +5     

Flag	Coverage Δ
apiserver-unittests	26.71% <0.00%> (-0.37%)	⬇️
core-unittests	54.61% <41.07%> (-0.03%)	⬇️
e2e-multicluster-test	23.30% <25.00%> (-0.17%)	⬇️
e2e-rollout-tests	31.05% <12.50%> (-0.07%)	⬇️
e2etests	36.23% <24.10%> (-0.34%)	⬇️

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

Impacted Files	Coverage Δ
apis/core.oam.dev/v1alpha1/envbinding_types.go	0.00% <ø> (ø)
pkg/appfile/parser.go	63.52% <17.64%> (-3.59%)	⬇️
...dev/v1alpha2/application/application_controller.go	71.54% <28.57%> (-1.15%)	⬇️
...r/core.oam.dev/v1alpha2/application/dispatch/gc.go	66.37% <48.00%> (-14.51%)	⬇️
...troller/core.oam.dev/v1alpha2/application/apply.go	84.12% <53.84%> (-2.32%)	⬇️
pkg/appfile/appfile.go	75.41% <63.63%> (-0.65%)	⬇️
....oam.dev/v1alpha2/application/dispatch/dispatch.go	77.58% <100.00%> (+0.26%)	⬆️
...ller/core.oam.dev/v1alpha2/application/revision.go	73.03% <100.00%> (+0.37%)	⬆️
...tepdefinition/workflowstepdefinition_controller.go	63.82% <0.00%> (-5.32%)	⬇️
pkg/utils/apply/apply.go	84.69% <0.00%> (-2.05%)	⬇️
... and 10 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8bcffb9...9cc9273. Read the comment docs.

[yangsoon]

cc @leejanee

[hongchaodeng]

What's the use case? Why keep those legacy resource?

[wangyikewxgm]

是否可以清理appRev的时候，清理对应对应的resourceTracker

[yangsoon]

是否可以清理appRev的时候，清理对应对应的resourceTracker

清理resourceTracker会导致历史资源被删除，后面会提供接口让用户主动去删

[wonderflow]

Need to write examples(docs) for this policy and usage. The docs don't need to show in our website, but contributors should be able to understand it

[yangsoon]

garbage-collect policy usages doc.

[wonderflow]

please fix CI

[leejanee]

please add scenes-oriented test cases.

[yangsoon]

please add scenes-oriented test cases.

https://github.com/oam-dev/kubevela/blob/213d699b9dd83e5a556aea01469518613b418f38/pkg/controller/core.oam.dev/v1alpha2/application/gc_test.go

[yangsoon]

The test coverage results seem to be incorrect, I am sure that the critical path has corresponding tests.
please cc @chivalryq