[Samsung] Docs template

[SS-JIA]

Summary:
Title says it all!

Add docs for the Samsung backend based on the template introduced in #14873.

---

Stack created with Sapling. Best reviewed with ReviewStack.

• -> [Samsung] Docs template #15087
• Add op support table #15086
• Prototype updated XNNPACK doc structure #15085

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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][CI] Machines under the label linux.rocm.gpu.2 are undergoing maintenance.

❌ 4 New Failures, 3 Pending, 1 Unrelated Failure

As of commit 9dd2292 with merge base 019c8da ():

NEW FAILURES - The following jobs have failed:

• Lint / link-check / lint-xrefs / linux-job (gh)
  RuntimeError: Command docker exec -t b37610cd6fab4ee5108531bf35af969b7af76561738db1de18fb3c29f46f9411 /exec failed with exit code 1
• pull / test-qnn-wheel-packages-linux (3.10) / linux-job (gh)
  RuntimeError: Command docker exec -t 006d777348d8cb762b7d51369c3ffb03734348925b705918bbf3749b0148cdba /exec failed with exit code 1
• pull / test-qnn-wheel-packages-linux (3.11) / linux-job (gh)
  RuntimeError: Command docker exec -t 01e1fda8a33db0ce00f3ed0abc091b26fe8857e74fe26e3c067a596509fe5ecd /exec failed with exit code 1
• pull / test-qnn-wheel-packages-linux (3.12) / linux-job (gh)
  RuntimeError: Command docker exec -t ee40ff134904a2865dafdf8386f4f3282d88c194fc02d4f19ad6c20655f30da8 /exec failed with exit code 1

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

• pull / unittest-arm-backend-with-no-fvp (test_pytest_models) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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.