Arm backend: Support boolean attention mask

[YufengShi-dudu]

• TOSA bitwise_* does not accept boolean inputs; attention masks often apply boolean bitwise operators that are equivalent to logical_*.

• Rename and extend RewriteBoolBitwiseNotToLogicalNotPass to RewriteBoolBitwiseToLogicalPass so bool bitwise_not/and/or/xor are rewritten to the corresponding aten.logical_* ops.

• Update and correct bitwise operator tests for bool inputs.

Change-Id: I5532f297587915d99213b8e597942fcc756ca7de

cc @digantdesai @SS-JIA @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures, 2 Cancelled Jobs

As of commit 5c2b5d0 with merge base 331ac4a ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t a74d069bc6503698ce97a21253fde661c5ae2da1ed7d224cc8f97c6a5b74a974 /exec failed with exit code 1
• pull / test-samsung-quantmodels-linux / linux-job (gh)
  RuntimeError: Command docker exec -t b9d8fae463a2c88ff8c0ce5c5d370a211e97d4e075b3581cd573373611d01acc /exec failed with exit code 1
• pull / unittest-editable / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_mv3_model
• trunk / test-arm-backend-vkml (test_pytest_ops_vkml) / linux-job (gh)
  RuntimeError: Command docker exec -t 921ab9e592304dcb227ef8198ec7fb492c578e5da8ee172dd981903ae478e866 /exec failed with exit code 1

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

• periodic (gh)
• trunk / test-models-macos-coreml (ic4) / macos-job (gh)
  ##[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.

[YufengShi-dudu]

@zingo I don't have the permission to add labels and run trunks now.