Fixes #3938

[yatiksihag01]

Description

• Fixed renaming issue while pasting conflicting files multiple times in same set of two directories.
• Disabled overwrite button if pasting in same directory. In previous implementation, we were showing users a Toast message if they try to overwrite a file in same directory. This new method seems more concise and more expressive.
• Set dialog shown during conflict resolution non-cancellable. This change ensures that users won't accidentally lose progress if they tap elsewhere on the screen.

Issue tracker

Fixes #3938

Automatic tests

• Added test cases

Manual tests

• Done

• Device: Samsung Galaxy A13
• OS: Android 13

Build tasks success

Successfully running following tasks on local:

• ./gradlew assembledebug
• ./gradlew spotlessCheck

Related PR

Related to PR #3898

[yatiksihag01]

Disabled overwrite button if pasting in same directory. In previous implementation, we were showing users a Toast message if they try to overwrite a file in same directory. This new method seems more concise and more expressive.

@VishnuSanal tell me what you think about it. Should we keep this implementation or the previous one in which we were showing a toast message.

[VishnuSanal]

Disabled overwrite button if pasting in same directory. In previous implementation, we were showing users a Toast message if they try to overwrite a file in same directory. This new method seems more concise and more expressive.

@VishnuSanal tell me what you think about it. Should we keep this implementation or the previous one in which we were showing a toast message.

@yatiksihag01 I vote for the new implementation. #3938 is fixed & works perfect! Consider this an approval from my side, let @VishalNehra & @TranceLove give approvals before merging.

PS: please fix the CI :)

PPS: apologies for the long hiatus in reviewing

[yatiksihag01]

Execution failed for task ':app:testPlayDebugUnitTest'.
Process 'Gradle Test Executor 27' finished with non-zero exit value 10
This problem might be caused by incorrect test process configuration.

I examined CI logs and found that this issue appears to be related to a org.gradle.api.tasks.TaskExecutionException. As you can see it suggest that error might be caused by incorrect test configuration. But I didn't change any test configuration. Additionally, there is limited online information available regarding the meaning of exit code 10. Initially Executor 27 initiated the test execution but finished with exit code 10 after the subsequent executors 28, 29,.., 31 had completed their tasks..
@VishnuSanal, @VishalNehra & @TranceLove any idea how can I fix it?

[VishnuSanal]

@yatiksihag01 I re-ran the CI & apparently it passes. @TranceLove please confirm whether we can ignore the previous failure.