[YUNIKORN-2667] E2E test for Gang app originator pod changes after restart

[blueBlue0102]

What is this PR for?

Add an E2E test to verify the Gang app originator pod changes after a restart.
Related to #855

What type of PR is it?

• - Improvement

What is the Jira issue?

YUNIKORN-2667

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.24%. Comparing base (085edca) to head (9c6b7f4).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #865      +/-   ##
==========================================
- Coverage   67.28%   67.24%   -0.04%     
==========================================
  Files          70       70              
  Lines        7609     7609              
==========================================
- Hits         5120     5117       -3     
- Misses       2271     2273       +2     
- Partials      218      219       +1     

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

[chenyulin0719]

Hi @blueBlue0102,
As we discussed offline, there is currently no way to check whether an allocation is the originator.
I think it's a good chance to expose the IsOriginator flag in REST.
I've created a Jira and assinged it to you.

• https://issues.apache.org/jira/browse/YUNIKORN-2722

[chenyulin0719]

+1 LGTM, waiting for E2E test pass.

[blueBlue0102]

The reason one of the E2E tests failed is due to a timeout error:
curl: (28) Failed to connect to archive.apache.org port 443 after 133360 ms: Connection timed out
@chenyulin0719 Could you please re-run the E2E test? Thanks!