Fix Default Enum and Ring asset path casing

[Ymenjour]

Summary

• normalize three Default Enum/Ring SVG paths from Assets to the canonical runtime assets tree
• restore exact-case resolution on Linux without adding a case-insensitive fallback
• leave the intentionally uppercase documentation and Image asset paths unchanged

Validation

• exhaustive exact-case scan of every SVG path referenced by Default .wfrog manifests: 84/84 unique paths resolve with exact Git casing; 0 mismatches and 0 missing paths
• Reference workspace and Widget layer only jobs pass on this head; the prior PR docs: expose format-first strategy note #14 runs stopped earlier on the missing lowercase Ring path
• dependent Graiphic/FROG-Runtime#1 Linux gate: 52/52 passed, 0 failed (run 31641758927)
• git diff --check: passed
• content blobs are unchanged; this PR contains three case-only renames

Repository-wide check status

The broader FROG workflows now pass resource validation and advance farther, but remain red on downstream debt: nine stale Reference Python UI expectations and one LLVM slice-05 assertion. Those corridors are not represented as fixed by this three-path PR, so it remains draft.

Dependency

Merge this PR before Runtime #1, then merge Graiph/FROG-STUDIO#2.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Youssef Menjour seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Youssef Menjour seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}