feat: reclaim device, deviceprofile and deviceservice before exiting YurtIoTDock

[wangxye]

What type of PR is this?

/kind feature
/sig iot

What this PR does / why we need it:

When YurtIoTDock receives the exit signal, it needs to reclaim device, deviceprofile, and deviceservice.
Clean up unwanted cr for users.

Which issue(s) this PR fixes:

Fixes #1626

Does this PR introduce a user-facing change?

NONE

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[LavenderQAQ]

/assign

[codecov]

Codecov Report

Merging #1647 (8bac380) into master (d89a805) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1647   +/-   ##
=======================================
  Coverage   51.66%   51.66%           
=======================================
  Files         145      145           
  Lines       17011    17011           
=======================================
  Hits         8788     8788           
  Misses       7407     7407           
  Partials      816      816           

Flag	Coverage Δ
unittests	51.66% <ø> (ø)

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

[LavenderQAQ]

I tried it on my own cluster and still couldn't seem to destroy the crd on exit.

kubectl get po
NAME                            READY   STATUS    RESTARTS   AGE
yurt-manager-5b8b997644-g8hhx   1/1     Running   0          6m44s

kubectl get device
NAME                                    NODEPOOL   SYNCED   AGE
beijing-random-binary-device            beijing    true     64s
beijing-random-boolean-device           beijing    true     64s
beijing-random-float-device             beijing    true     64s
beijing-random-integer-device           beijing    true     64s
beijing-random-unsignedinteger-device   beijing    true     64s
beijing-sample-image                    beijing    true     64s
beijing-sample-json                     beijing    true     64s
beijing-sample-numeric                  beijing    true     64s
...

[LavenderQAQ]

@wangxye Sorry, it's the problem with my local shell workflow. The pr test should be fine.

[LavenderQAQ]

/lgtm

[openyurt-bot]

@LavenderQAQ: changing LGTM is restricted to collaborators

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openyurt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LavenderQAQ, rambohe-ch, wangxye

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rambohe-ch]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rambohe-ch]

/lgtm