[BUG] YurtIoTDock cannot sync device/deviceprofile/deviceservice info from edgex3.0

[LavenderQAQ]

What happened:
YurtIoTDock has been successfully deployed.

kubectl get po
NAME                                                              READY   STATUS    RESTARTS      AGE
edgex-app-rules-engine-beijing-mv7kg-857fc789d8-5g7hb             1/1     Running   0             27s
edgex-core-command-beijing-kpnwl-7b96c5bfdb-qm6c2                 1/1     Running   0             27s
edgex-core-common-config-bootstrapper-beijing-z2rfd-b9cbbdrbfb4   1/1     Running   0             26s
edgex-core-consul-beijing-xnz9v-6fd76888c-qcws5                   1/1     Running   0             27s
edgex-core-data-beijing-q94vd-6fc75c8488-skmvk                    1/1     Running   0             27s
edgex-core-metadata-beijing-k7bh9-6f8d76fb44-9tbgj                1/1     Running   0             27s
edgex-device-rest-beijing-bjxpl-5c44b54448-wnh6l                  1/1     Running   2 (14s ago)   27s
edgex-device-virtual-beijing-tfpnl-5b548b889c-mz2ld               1/1     Running   1 (14s ago)   27s
edgex-kuiper-beijing-crjd6-54d7d6b889-sqgpf                       1/1     Running   0             27s
edgex-redis-beijing-5zsqr-66b4f7b4d4-kb5gx                        1/1     Running   0             27s
edgex-support-notifications-beijing-wvg7f-fd8c7855d-cs9pt         1/1     Running   0             26s
edgex-support-scheduler-beijing-qndq5-68cb75489f-pqzsh            1/1     Running   0             26s
edgex-ui-go-beijing-q7kgm-f7c6f658b-bf726                         1/1     Running   0             27s
yurt-iot-dock-beijing-zwdkz-68449cbc4d-29nmp                      1/1     Running   0             26s
yurt-manager-5b8b997644-ztm6w                                     1/1     Running   0             11m

However, data related to the device cannot be synchronized

kubectl get deviceservice
No resources found in default namespace.

kubectl get deviceprofile
No resources found in default namespace.

kubectl get device
No resources found in default namespace.

What you expected to happen:
In versions prior to 3.0, YurtIoTDock could sync to device info.

kubectl get device
No resources found in default namespace.

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

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

How to reproduce it (as minimally and precisely as possible):

apiVersion: iot.openyurt.io/v1alpha2
kind: PlatformAdmin
metadata:
  name: edgex-sample
spec:
  version: minnesota
  poolName: beijing

Anything else we need to know?:
Should be related to the change of edgex3.0, the configuration of edgex has changed a lot in version 3.0.

Environment:

• OpenYurt version: master
• Kubernetes version (use kubectl version): 1.22.15
• OS (e.g: cat /etc/os-release): ubuntu
• Kernel (e.g. uname -a): Linux hanqi-code 5.4.0-148-generic
• Install tools: kind

others

/kind bug

[wangxye]

/assign

[LavenderQAQ]

This issue has been solved by this pr.