add(scan): Add the scan_start_where_left test to CI

[upbqdn]

Motivation

Close #8085.

PR Author Checklist

Check before marking the PR as ready for review:

• Will the PR name make sense to users?
• Does the PR have a priority label?
• Have you added or updated tests?
• Is the documentation up to date?

Solution

• Add a new job named scan-start-where-left-test to the Integration Tests on GCP workflow.

Reviewer Checklist

Check before approving the PR:

• Does the PR scope match the ticket?
• Are there enough tests to make sure it works? Do the tests cover the PR motivation?
• Are all the PR blockers dealt with?
  PR blockers can be dealt with in new tickets or PRs.

And check the PR Author checklist is complete.

[upbqdn]

Let's see if the new job actually runs in the CI.

[upbqdn]

@arya2 thanks for the fix!

I looked at our Dockerfile, and I noticed we build the test binaries when building the image: https://github.com/zcashfoundation/zebra/blob/88dd18adb7db6e6127da578d9d7aaa7cab869fe9/docker/Dockerfile#L133-L134.

The new job in this PR runs the tests here https://github.com/zcashfoundation/zebra/blob/88dd18adb7db6e6127da578d9d7aaa7cab869fe9/docker/entrypoint.sh#L183 with a different set of features. That means the tests are rebuilt each time the job runs anyway. I wonder if we could omit building the tests in the Dockerfile.

Edit: The answer is no because only a small subset of the crates is recompiled. If we omitted the building in the Dockerfile, each job would need to rebuild all of the crates.