Fix the context choosing error after migration case.

[blackpiglet]

Try to use the normal import way in ginkgo tests.
Change the FAIL_FAST default value to false.

Thank you for contributing to Velero!

Please add a summary of your change

Does your change fix a particular issue?

Fixes #(issue)

Please indicate you've done the following:

• Accepted the DCO. Commits without the DCO will delay acceptance.
• Created a changelog file (make new-changelog) or comment /kind changelog-not-required on this PR.
• Updated the corresponding documentation in site/content/docs/main.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.19%. Comparing base (ba0dbb9) to head (6a1d8df).
Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8293      +/-   ##
==========================================
- Coverage   59.20%   59.19%   -0.02%     
==========================================
  Files         367      367              
  Lines       30838    30840       +2     
==========================================
- Hits        18259    18255       -4     
- Misses      11119    11124       +5     
- Partials     1460     1461       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[renmaosheng]

what is the impact for this change? will it take more time for testing?

[blackpiglet]

The FAIL_FAST flag determines how to handle errors met during the test suite running.
If FAIL_FAST is set to true, the test suite stops running immediately.
If FAIL_FAST is set to false, the test suite continues running on meeting test error.

The FAIL_FAST flag is introduced to help debug the test error, so set the default value to false, and let the Jenkins pipeline can pass the value to determine whether the flag should be turned on.

[reasonerjt]

lgtm