Implement internal cropping instead of library's built-in function

[terofeev]

What is it?

• Bugfix
• Feature
• Codebase improvement

Description of the changes in your PR

• Fix saving an unnecessary copy when cropping and resizing a picture.
• Reuse the library's built-in progress bar to indicate the cropping process.

Before/After Screenshots/Screen Record

• Before:

Before.mp4

• After:

After.mp4

Fixes the following issue(s)

• Fixes After edit picture, a copy is saved in app data #378

Acknowledgement

• I read the contribution guidelines.

[naveensingh]

Thanks for the PR!

• A temporary file is still created when you press the share button.
• Alternatively, we could build, pass, manage a custom output Uri ourselves, that seems to be the "recommended" solution by the developer.

[terofeev]

Thanks for your comment!
I've fixed the share option.

I reviewed the "recommended" solution by the developer, but it comes with a few drawbacks:

• We still create at least one temporary image.
• The share option always generates its own copy via getTempImagePath, storing it in the app’s cache/images directory.
• This approach unnecessarily consumes device resources like CPU, storage, etc.

So, in a new commit, I've completely switched to using our own cropping method without saving temporary images.

[naveensingh]

Okay, thanks!

I'll do some final testing and merge soon.