v1.18: ci: skip spl test when version is too high (backport of #1945)

[mergify]

Problem

it makes no sense to run spl tests with lower version. actually we did it before but the logic missed accidentally. solana-labs#27326

Summary of Changes

stop running spl tests when it bump to higher version

---

This is an automatic backport of pull request #1945 done by Mergify.

[mergify]

Cherry-pick of 4d9d27f has failed:

On branch mergify/bp/v1.18/pr-1945
Your branch is up to date with 'origin/v1.18'.

You are currently cherry-picking commit 4d9d27f1ff.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .github/scripts/downstream-project-spl-common.sh

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/workflows/downstream-project-spl.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[yihau]

skip! https://github.com/anza-xyz/agave/actions/runs/9754992611/job/26922776717#step:5:145

[steviez]

LGTM - I made some comments about why this is needed on the v2.0 BP PR, those comments apply here as well except that v1.18 CI is actually broken without this change.

Lastly, as @yihau pointed out in #1960 (comment), we can see that the check is working as intended here on the v1.18 branch

[CriesofCarrots]

Needs rebase?

[steviez]

Needs rebase?

Yeah, we should be able to get all greens with rebase. I was hesitant to rebase it and make my ship it not count towards the two necessary to push, but let's rebase and we can voluntell one more reviewer.

Edit: Oh wait, I forgot; rebase won't clear the reviews!

[CriesofCarrots]

Oh wait, I forgot; rebase won't clear the reviews!

Yeah, I always forget this too! It's nice that github has gotten more rational in this one case.