Update cpuinfo pin to latest

[pytorchbot]

This PR was created by the merge bot to help merge the original PR into the main branch.
ghstack PR number: #13605 by @kimishpatel
^ Please use this as the source of truth for the PR details, comments, and reviews
ghstack PR base: https://github.com/pytorch/executorch/tree/gh/kimishpatel/197/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/kimishpatel/197/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/kimishpatel/197/orig
@diff-train-skip-merge

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure

As of commit a1edfd1 with merge base 45e7810 ():

NEW FAILURE - The following job has failed:

• pull / unittest / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 5

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

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

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

[digantdesai]

Do we also want to (1) update pytorch/pytorch, (2) pull it internally?

[digantdesai]

Nit: Can you add rationale for what's the reason(s) for upgrading in the PR summary, for posterity.

Thanks.

[kimishpatel]

Nit: Can you add rationale for what's the reason(s) for upgrading in the PR summary, for posterity.

Thanks.

I think @ykhrustalev asked for it. I think some features went in that they depend on. Didnt ask for details though. @ykhrustalev if you provide details i can add

[kimishpatel]

Do we also want to (1) update pytorch/pytorch, (2) pull it internally?

Not sure of having to keep it in sync with pytorch/pytorch but if we do 2 I suppose we have to do 1. I will update internal first

[ykhrustalev]

@kimishpatel @digantdesai the windows aarch64 cross compilation fix pytorch/cpuinfo#311