Fix 'occured' -> 'occurred' typos in backends and exir tracer

[SAY-5]

Nine error messages used the misspelled occured:

• backends/apple/mps/runtime/MPSDevice.mm:141 — additionally had a duplicated occured occured (An error occured occured while compiling library %d).
• backends/cadence/hifi/operators/op_quantized_matmul_out.cpp × 3
• backends/cadence/hifi/operators/op_quantized_matmul_asym8uxasym8u_asym8u_out.cpp × 3
• backends/cadence/hifi/operators/op_quantized_matmul_asym8sxasym8s_asym8s_out.cpp × 3
• exir/tracer.py — torchdynamo internal-error format string

All ET_CHECK_MSG and printf-style messages reach end users in build / runtime error output, and the dynamo tracer message is logged on every dynamo trace failure. Python ast.parse clean for the touched tracer.py; .cpp/.mm changes are string-literal-only with no logic touched.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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! (3 Unrelated Failures)

As of commit 521361e with merge base 75fe8e9 ():

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / test-llama-runner-linux (fp32, xnnpack+custom+qe, linux.2xlarge, executorch-ubuntu-22.04-clang12) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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

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

• pull / unittest / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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.

[SAY-5]

/release-notes none

This is a typo-only fix to error message strings — no user-facing behaviour change.

[JacobSzwejbka]

thanks