[WIP] replace full sync static sleeps with full sync trigger API calls

[sashrith]

What this PR does / why we need it:

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Testing done:
A PR must be marked "[WIP]", if no test result is provided. A WIP PR won't be reviewed, nor merged.
The requester can determine a sufficient test, e.g. build for a cosmetic change, E2E test in a predeployed setup, etc.
For new features, new tests should be done, in addition to regression tests.
If jtest is used to trigger precheckin tests, paste the result after jtest completes and remove [WIP] in the PR subject.
The review cycle will start, only after "[WIP]" is removed from the PR subject.

Special notes for your reviewer:

Release note:

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sashrith

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• tests/e2e/OWNERS [sashrith]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[svcbot-qecnsdp]

Started Vanilla block pre-checkin pipeline... Build Number: 2256

[svcbot-qecnsdp]

Build ID: 2256
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
Ran 1 of 743 Specs in 739.506 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 742 Skipped
--- FAIL: TestE2E (739.59s)
FAIL

Ginkgo ran 1 suite in 23m15.475996216s

Test Suite Failed

[svcbot-qecnsdp]

Started vanilla Block pipeline... Build Number: 2033

[svcbot-qecnsdp]

Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
Ran 1 of 765 Specs in 153.921 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 764 Skipped
--- FAIL: TestE2E (153.97s)
FAIL

Ginkgo ran 1 suite in 3m29.242239883s

Test Suite Failed

[svcbot-qecnsdp]

Started vanilla Block pipeline... Build Number: 2124

[svcbot-qecnsdp]

Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
Ran 68 of 788 Specs in 15172.322 seconds
FAIL! - Interrupted by User -- 57 Passed | 11 Failed | 0 Pending | 720 Skipped
--- FAIL: TestE2E (15172.45s)
FAIL

Ginkgo ran 1 suite in 4h14m1.979563339s

Test Suite Failed

[svcbot-qecnsdp]

Block vanilla build status: FAILURE 
Stage before exit: checkout 

[svcbot-qecnsdp]

Started vanilla Block pipeline... Build Number: 2211

[svcbot-qecnsdp]

Block vanilla build status: SUCCESS 
Stage before exit: finally 

[svcbot-qecnsdp]

Started vanilla Block pipeline... Build Number: 2213

[svcbot-qecnsdp]

Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
Ran 132 of 812 Specs in 11694.643 seconds
FAIL! -- 40 Passed | 92 Failed | 0 Pending | 680 Skipped
--- FAIL: TestE2E (11695.10s)
FAIL

Ginkgo ran 1 suite in 3h16m46.470495559s

Test Suite Failed

[k8s-ci-robot]

PR needs rebase.

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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale