bypass add and addRelu that have inputs from non-dq nodes

[rezaasjd]

Summary:
The QuantFusion pass in crashes when an add node's inputs aren't dequantize_per_tensor ops. QAT model produces exactly this pattern.
The dequants_inputs list ends up empty, and get_args_and_kwargs_add() indexes [0].

Differential Revision: D103949573

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 Awaiting Approval, 2 New Failures, 4 Unrelated Failures

As of commit 0758007 with merge base 5d07ce0 ():

AWAITING APPROVAL - The following workflow needs approval before CI can run:

• Lint (gh)

NEW FAILURES - The following jobs have failed:

• Build Presets / apple (ios-simulator) / build (gh)
  The process '/opt/homebrew/bin/git' failed with exit code 128
• pull / test-qnn-delegate-linux / linux-job (gh)
  backends/qualcomm/tests/test_qnn_delegate.py::TestQNNFloatingPointOperator::test_qnn_backend_argmax

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

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

• pull / unittest / linux / linux-job (gh) (trunk failure)
  examples/models/llama/tests/test_static_attention.py::StaticAttentionTest::test_within_transformer
• pull / unittest / macos / macos-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)
  examples/models/llama/tests/test_static_attention.py::StaticAttentionTest::test_within_transformer
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)
  ##[error]The operation was canceled.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-codesync]

@rezaasjd has exported this pull request. If you are a Meta employee, you can view the originating Diff in D103949573.

[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.