test: optimize the time of run test cases

[HusterWan]

Signed-off-by: ziren.wzr ziren.wzr@alibaba-inc.com

Ⅰ. Describe what this PR did

Since our integration test cases run about 30mins, the more test cases, the longer the running time.

So, we can optimize some test cases to decrease the running time, like:

• first stop the container with timeout 1 then delete it
• add timeout to 1 when stop a container

Let's see if we can decrease the running time of the integration test cases :)

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

[codecov]

Codecov Report

Merging #2621 into master will decrease coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2621      +/-   ##
==========================================
- Coverage   69.07%   68.99%   -0.08%     
==========================================
  Files         279      279              
  Lines       18834    18834              
==========================================
- Hits        13009    12995      -14     
- Misses       4360     4372      +12     
- Partials     1465     1467       +2

Flag	Coverage Δ
#criv1alpha1test	31.42% <ø> (+0.04%)	⬆️
#criv1alpha2test	35.65% <ø> (-0.07%)	⬇️
#integrationtest	41.16% <ø> (-0.03%)	⬇️
#nodee2etest	32.74% <ø> (-0.12%)	⬇️
#unittest	26.78% <ø> (ø)	⬆️

Impacted Files	Coverage Δ
pkg/streams/utils.go	82.14% <0%> (-9.53%)	⬇️
apis/server/utils.go	71.15% <0%> (-3.85%)	⬇️
daemon/mgr/spec_linux.go	76.74% <0%> (-1%)	⬇️
ctrd/container.go	58.1% <0%> (-0.8%)	⬇️
daemon/mgr/container.go	58.79% <0%> (-0.43%)	⬇️
cri/v1alpha2/cri.go	68.06% <0%> (-0.13%)	⬇️
cri/v1alpha2/cri_wrapper.go	66.8% <0%> (+1.2%)	⬆️
ctrd/image.go	78.18% <0%> (+2.27%)	⬆️

[HusterWan]

before this pr:

after this pr:

Saved 3 minutes

[allencloud]

This helps a lot for #1184.

[allencloud]

LGTM