updated cmake and doc for bundled program

[Gasoonjia]

Summary:
CMake and Doc Updates for Bundled Program

This diff includes the following changes:

Doc Updates

• Updated bundled-io.md to reflect changes in the getting-started and export-to-executorch-tutorial links.

CMake Updates

• Updated build_example_runner.sh to simplify the build process and fix the pipefail issue.
• Updated test_example_runner.sh to use the same build script as build_example_runner.sh and remove redundant code.

Reviewed By: larryliu0820, lucylq

Differential Revision: D84526104

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• [ROCm][CI] Machines under the label linux.rocm.gpu.2 are undergoing maintenance.

❌ 1 New Failure, 3 Pending, 2 Unrelated Failures

As of commit e78d966 with merge base d382f6b ():

NEW FAILURE - The following job has failed:

• Build Presets / windows (windows) / build (gh)

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

• pull / unittest / windows / windows-job (gh) (detected as infra flaky with no log or failing log classifier)

BROKEN TRUNK - The following job failed but was present on the merge base:

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

• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  runtime/test/test_runtime_etdump_gen.py::RuntimeETDumpGenTest::test_etdump_params_with_bytes_and_buffer

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

[meta-codesync]

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

[larryliu0820]

Review automatically exported from Phabricator review in Meta.

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

[Gasoonjia]

@pytorchbot cherry-pick --onto release/1.0 -c docs

[pytorchbot]

Cherry picking #15081

The cherry pick PR is at #15093 The following tracker issues are updated:

• [v1.0.0] Release Tracker #14288 (comment)

Details for Dev Infra team

Raised by workflow job