fix renamed enum and struct re-exports in rust codegen

[amirHdev]

Summary

Fix a compiler issue where renamed exported enums and structs could lose their public identity during
import or re-export resolution.

Fixes #9094

Update

The major problem was that renamed public identities are needed for Rust codegen but plain alias imports must still remain semantically.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f5b320d65d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[ogoffart]

Thanks for tackling this issue.
Could you also make a test in tests/cases/export
(you can maybe extend tests/cases/export/named_export by re-declaring structs of the same name in the rust and cpp part)

The other problem is that this is a breaking change and i don't know if this is acceptable.
Perhaps an alternative would be to keep the export as deprecated, as i write in #9094 (comment)
(this can be tested with the #[expect(deprecated)] when using it in a rust block in tests/cases

[amirHdev]

The other problem is that this is a breaking change and i don't know if this is acceptable. Perhaps an alternative would be to keep the export as deprecated, as i write in #9094 (comment) (this can be tested with the #[expect(deprecated)] when using it in a rust block in tests/cases

To make that design correct we’d need to decide whether the old name should stop being a normal public export in those cases which is a larger API shape.