[BREAKING] fix!: Include original file extension in retargeted drawables on Android

[MartinZikmund]

GitHub Issue (If applicable): part of #15866, closes #9618

PR Type

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Docs have been added/updated which fit documentation template (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Validated PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Associated with an issue (GitHub or internal) and uses the automatic close keywords.
• Commits must be following the Conventional Commits specification.

Other information

Internal Issue (If applicable):

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-15891/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-15891/index.html

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-15891/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-15891/index.html

[jeromelaban]

This is a breaking change for apps that use this type of assets natively on android. why is it required?

[MartinZikmund]

This is a breaking change for apps that use this type of assets natively on android. why is it required?

It follows up investigation of #15866, but I have hit it before as well. The issue is that while on all targets the extension of the image is significant, on Android the extension is ignored and only one of the files is ultimately usable. I guess it is an edge case, but we should either do this or at least warn the user or show an error, when we are retargeting two assets with the same name on Android

[jeromelaban]

@MartinZikmund I see. The origin of the issue is caused by duplicate files, which should not happen in the first place as I understand. We may make this change in our next major, but it's a very subtle break that is not easy to spot.