Add strict-flag to ExportSession

[Erik-Lundell]

**Add strict export option to ExportRecipe**

Default is True, mirroring earlier behavior.
Also update ExportSession to handle this.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218

[pytorch-bot]

🔗 Helpful Links

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

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

As of commit c06c386 with merge base 3b16bc1 ():

NEW FAILURE - The following job has failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 6373da704ec5b3e2028869d433de9b78b98de65c549e2040171b9d09ca295149 /exec failed with exit code 1

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

• pull / test-llama-runner-linux-android / linux-job (gh) (matched linux rule in flaky-rules.json)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

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

[digantdesai]

I think this is going to be a general problem for all "non-partitioner" op-lib backends. My thinking is we should either hide them behind a pseudo-partitioner wrapper to make it more composible. For now this might be OK. See some comments I added here. Stamping to unblock. Let's try to resolve the comments before merging.

[Erik-Lundell]

Ack, I removed the post_edge commit from this PR and will create a new with the post-to-backend stage.