Trial revert of --use-pt-pinned-commit for llava

[swolchok]

Now that we've bumped the nightly version, let's make sure that --use-pt-pinned-commit is definitely causing the long running times here (#8180).

[swolchok]

Stack from ghstack (oldest at bottom):

• -> Trial revert of --use-pt-pinned-commit for llava #8193

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• ROCM Infra failures during checkout of PyTorch

❌ 2 New Failures

As of commit caec336 with merge base a3455d9 ():

NEW FAILURES - The following jobs have failed:

• Check Labels / Check labels (gh)
  RuntimeError: Error checking labels: PR does not have required labels
• pull / unittest / macos / macos-job (gh)
  backends/xnnpack/test/passes/test_channels_last_tagged_reshape.py::TestChannelsLastTaggedReshapePass::test_qs8_channels_last_tagged_reshape_pass

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

[github-actions]

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.