Support sine operator on XNNPACK

[pytorchbot]

Summary: Wire up the unary sine operator in xnnpack for fp32 and fp16.

Differential Revision: D83623086

[pytorch-bot]

🔗 Helpful Links

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

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

As of commit 2e2916b with merge base e0dda90 ():

NEW FAILURE - The following job has failed:

• pull / test-llava-runner-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 70f3ae2900bb64a568deb97749e3da3480662123190e1eff1d973d93123a0085 /exec failed with exit code 1

CANCELLED JOBS - The following jobs were cancelled. Please retry:

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

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.

[GregoryComer]

@digantdesai This is causing a very slight difference in output in the llava runner ("photo" -> "photograph"), causing the test to fail. This appears benign. Since you requested the pick, I'll defer to you. Is this a concern? Should I land it and forward fix the test on the branch? Or drop the pick? Given that it's conceptually low risk, I'm okay to merge it this afternoon, but any later and I will need to drop it.

Edit: It looks like the test was disabled on main in #14285 but not picked.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.