xtensa-esp32-elf: Rename into xtensa-esp-elf

[pembem22]

• xtensa-esp32/esp32s2/esp32s3-elf were unified into xtensa-esp-elf, see the release notes.

• Update manifest accordingly.

• [x] I have read the Contributing Guide.

[pembem22]

/verify

[github-actions[bot]]

All changes look good.

Wait for review from human collaborators.

xtensa-esp-elf

• [x] Description
• [x] License
• [x] Hashes
• [x] Checkver
• [x] Autoupdate
• [x] Autoupdate Hash Extraction

[tech189]

We should try to avoid renaming manifests as users might get stuck on the old one and not realise that their app is no longer being updated (there is no current way to migrate users to the updated name). I feel like this may be too minor a name change to warrant a rename. Especially as all the binaries are still xtensa-esp32*-elf anyway. What do you think @HUMORCE?

[HUMORCE]

Scoop Core does not provide features like aliases, indicating alternatives, or disabling manifests, currently. I would prefer to add a deadline and announcement to notes of the original manifest and keep its functions (autoupdate, etc.), then create a new one.

https://github.com/ScoopInstaller/Extras/pull/11116 https://github.com/ScoopInstaller/Extras/pull/11171 And a manifest that is plagued by name changes: https://github.com/ScoopInstaller/Extras/pulls?q=is%3Apr+foxit