Media files are sometimes uploaded with path to local storage (Aztec version)

We've been seeing a few reports of images being uploaded to the app with a path to local storage. For example:

https://example.com/data/user/0/org.wordpress.android/cache/img_75591360079905.jpg

There's a similar report to this in https://github.com/wordpress-mobile/WordPress-Android/issues/10203 which contains steps to replicate for the block editor. I'm separating this report out from the comments of that one, as we've also had reports from users who use Aztec.

An example of such a report is in 2727375-zen. The user noted the following about their specific case:

• They upload images straight from their device to the post editor by tapping the + icon.
• They always wait for the image to finish uploading before making any other changes or navigating away from the editor.
• They also always make sure to manually save the post before exiting.
• They've been able to replicate the issue on multiple different connections, as they're travelling at the moment.
• Their site is hosted on WordPress.com.
• They're using version 14.1 of the app and have a Samsung SM-A505FN.

We've been unable to replicate the issue with the Aztec editor so far, and it's unlikely the fix for https://github.com/wordpress-mobile/WordPress-Android/issues/10203 will address the issues for Aztec.

Although we don't yet have steps to replicate, I wanted to create a report for further troubleshooting and gathering details.

Start by reviewing issue #10203 and its block-editor reproduction steps, then compare them with the Aztec editor flow described here. Investigate how images selected via the + icon are uploaded and persisted, using the reported local-storage path as the failure symptom. Done means the Aztec-specific cause is identified and a reproducible verification path is available.