[slimtensor migration 3/n] use et_check instead of standalone check

[Gasoonjia]

Stack from ghstack (oldest at bottom):

• [slimtensor migration 6/n] add copyright headers #16330
• [slimtensor migration 5/n] reuse et c10 headers #16329
• [slimtensor migration 4/n] use ET ArrayRef and IntArrayRef #16327
• -> [slimtensor migration 3/n] use et_check instead of standalone check #16314
• [slim tensor migration 2/n] update slimtensor namespace #16313
• [slim tensor migration 1/n] copy and paste slim tensor into ExecuTorch #16304

This stack aims to migrate slim tensor into ExecuTorch stack to make it as internal tensor representation of cudabackend.

This diff replace origianl standalone_check with et_check to meet et standard

Differential Revision: D89445966

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 1 Cancelled Job, 1 Unrelated Failure

As of commit 095cf3b with merge base c61b2ed ():

NEW FAILURE - The following job has failed:

• pull / unittest-arm-backend-with-no-fvp (test_pytest_models) / linux-job (gh)
  RuntimeError: Command docker exec -t 5201d2aede546e58236b01957827d5ca0d0b61119198b4c4bdd1b3106ec84c3f /exec failed with exit code 1

CANCELLED JOB - The following job was cancelled. Please retry:

• pull / test-samsung-models-linux / linux-job (gh)
  ##[error]The operation was canceled.

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• pull / android / run-emulator (gh) (#16137)
  Timeout waiting for emulator to boot.

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.