Fix amazon release build from github actions

[mikehardy]

Checked for duplicates?

• [X] This issue is not a duplicate

What are the steps to reproduce this bug?

Run publish release workflow with "public" release specified This should trigger the amazon release (or an attempt to release to amazon...)

Expected behaviour

Successful release

Actual behaviour

Running 'publishToAmazonAppStore' gradle target
Starting a Gradle Daemon, 4 stopped Daemons could not be reused, use --status for details

> Configure project :
CI build detected: setting compiler execution strategy to IN_PROCESS

> Task :AnkiDroid:publishToAmazonAppStore
️🔒 Authenticating...
️↕️️ Deleting edit...
⬅️ Remove APKs from previous edit...

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':AnkiDroid:publishToAmazonAppStore'.
> ❌ Failed to delete existing APK

Debug info

https://github.com/ankidroid/Anki-Android/actions/runs/5676011762/job/15382106501#step:10:605

(Optional) Anything else you want to share?

Probably need to sort this out manually a few times, but amazon is a lower priority than getting play store + github releases working, and then F-Droid full builds

Research

• [X] I am reporting a bug specific to AnkiDroid (Android app)
• [X] I have checked the manual and the FAQ and could not find a solution to my issue
• [X] (Optional) I have confirmed the issue is not resolved in the latest alpha release (instructions)

[lukstbit]

As a note:

I created a PR for that plugin to update the dependencies(most likely it doesn't fix this issue). The author responded and said he'll take a look at the plugin later in august.

[github-actions[bot]]

Hello 👋, this issue has been opened for more than 3 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically

[Nishthajain7]

Is this issue still open? Can I take it up?