Fix trunk ci

[lucylq]

Summary

The problem is:

1. In tests, Verification::InternalConsistency is requested.
2. In release builds, ET_ENABLE_PROGRAM_VERIFICATION=False.
3. Check flatbuffer offset when verification is minimal #18597 returned a hard error when Verification::InternalConsistency was requested but not available (ie when 1 and 2 conflict)

This PR reverts the hard error and falls back to Verification::Minimal when Verification::InternalConsistency is required but not available (e.g. in Release builds)

Test plan

CI

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 3 Unrelated Failures

As of commit 0620178 with merge base 19f7ff2 ():

NEW FAILURES - The following jobs have failed:

• Cadence Build & Test / cpu-test / test-ops / test-ops (gh)
  examples/cadence/operators/test_g3_ops.py::ATenOpTestCases::test_g3_neg_out_0
• trunk / unittest-release / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_mv3_model

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 / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• trunk / unittest-release / windows / windows-job (gh) (trunk failure)
  ##[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.

[Copilot]

Pull request overview

Adjusts Program::load() verification behavior to avoid failing CI/tests when Verification::InternalConsistency is requested but program verification is compiled out (e.g., Release builds), by gracefully falling back to minimal verification.

Changes:

• Replaces the hard error on InternalConsistency requests when ET_ENABLE_PROGRAM_VERIFICATION is disabled with an informational log and fallback behavior.
• Ensures the minimal root-table-offset bounds check also runs for InternalConsistency requests when full verification isn’t available.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The comment about InternalConsistency here is now misleading in builds where ET_ENABLE_PROGRAM_VERIFICATION is disabled: in that configuration an InternalConsistency request falls back and VerifyProgramBuffer is not called above. Consider rewording to clarify that the root-offset check is redundant only when InternalConsistency verification is actually available/enabled.

Suggested change

	// In InternalConsistency mode this is done by VerifyProgramBuffer above.
	// This check is also covered by VerifyProgramBuffer when full
	// InternalConsistency verification is enabled and runs above.

[abhinaykukkadapu]

Looks good, thanks for fixing it fast.