don't double-install executorch for one-off linux pull-time jobs

[swolchok]

I remember somebody mentioning they wanted install_executorch to be the one solution previously. CI is red for these jobs due to timeouts and we should not block a time improvement just because it is not the ideal long-term solution.

[swolchok]

Stack from ghstack (oldest at bottom):

• Optionally move setup.py/pip cmake-out to repo_root/cmake-out #7720
• -> don't double-install executorch for one-off linux pull-time jobs #8142

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/8142

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (2 Unrelated Failures)

As of commit 62f7f19 with merge base 637cc32 ():

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / test-eval_llama-mmlu-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-llava-runner-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[dbort]

I was going off of old information, and was afraid that this change would remove all CI testing of install_executorch.sh.

In the past, the CI setup scripts did their own version of install_executorch, but now it calls down to the script:

executorch/.ci/scripts/utils.sh

Line 23 in 821a2fe

install_executorch() {

So this looks good! Thanks for removing these.