Update Muse Glimmer GGUF filenames to canonical names

[sid-rp]

Summary

The meta-models/Muse-Glimmer-30B-GGUF repo standardized its GGUF filenames to canonical Q4_K names. The old-named files are being removed, so this updates ExecuTorch to reference the canonical names.

Rename map

Old	New
muse-glimmer-30B-kquant-17gb.gguf	Muse-Glimmer-30B-KQuant-17GB-Q4_K_M.gguf
muse-glimmer-30B-kquant-dynamic.gguf	Muse-Glimmer-30B-KQuant-Dynamic-Q4_K_XL.gguf
dflash-kquant.gguf	dflash-Muse-Glimmer-30B-Q4_K_M.gguf
mmproj-kquant.gguf	mmproj-Muse-Glimmer-30B-Q4_K_M.gguf

Files changed

• .ci/scripts/export_model_artifact.sh — the hf_hub_download target/draft/mmproj filenames (the kquant-17gb / kquant-dynamic quant-mode CLI args are unchanged — only the downloaded .gguf filenames)
• examples/models/muse-glimmer/README.md — file table + find snippets
• examples/models/muse-glimmer/export/export_solo.py — --gguf / --mmproj help text examples
• examples/models/muse-glimmer/export/export_dflash.py — --target-gguf / --draft-gguf help text examples

Notes

• Pure string rename — no logic changes. All 4 new names verified to exist on the HF repo (case-sensitive exact match).
• The README download step uses --include '*.gguf', so it already fetches the canonical files; no change needed there.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

⏳ No Failures, 361 Pending

As of commit e2ee85a with merge base 287ab8b ():
💚 Looks good so far! There are no failures yet. 💚

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: sid-rp / name: sid-rp (e2ee85a)

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