CI e2e improvement

[kason-huang]

In the current CI e2e process, there are some bugs we need to fix and improvement we need to do.

• [x] If the creation of a pod fails, the creation request is not sent again, and the e2e test will failed. It needs to be optimized to add a retry if the creation of a pod fails. https://github.com/kubeedge/edgemesh/runs/3607557974?check_suite_focus=true https://github.com/kubeedge/edgemesh/pull/110
• [ ] Use docker to simulate more nodes to do more tests.
• [x] Delete the hostport in the e2e test code, because we no longer have hostport restrictions。 https://github.com/kubeedge/edgemesh/blob/main/tests/e2e/k8s/tools.go#L136
• [ ] Try to using the kubectl log on the edge to fetch the log ranther than using docker logs in the script code
• [x] CI e2e retry times is 20, we should set the retry times to 2 or 3
• [ ] CI e2e test support differenct config for edgemesh, such as test open tls and close tls feature both.
• [x] Use helm to deploy edgemesh in shell bash.
• [ ] Use unity the script in https://github.com/kubeedge/edgemesh/issues/221 to config kubeedge

[kason-huang]

/good-first-issue

[kubeedge-bot]

@khalid-jobs: This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.