Fix max-pixels compression not applying to ImageWidget

[grzesiek2010]

Closes #7277

Why is this the best possible solution? Were any other approaches considered?

We recently refactored ImageWidget and detached it from the old hierarchy (it previously extended BaseImageWidget). As a result, we now need to explicitly handle it in MediaLoadingTask, where we determine whether image compression should be triggered.

This is probably not the ideal architecture (although it has been working this way for a long time), as MediaLoadingTask is responsible for more than just image loading. A better long-term solution would be to move the compression logic into the image widgets themselves. However, that would require a larger refactoring, and with the release just around the corner, this doesn't seem like the right time for such a change.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

The fix is tiny and carries virtually no risk. A simple check to verify that compression works for basic image widgets is sufficient.

Do we need any specific form for testing your changes? If so, please attach one.

There's a form attached to the issue.

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No.

Before submitting this PR, please make sure you have:

• added or modified tests for any new or changed behavior
• run ./gradlew connectedAndroidTest (or ./gradlew testLab) and confirmed all checks still pass
• added a comment above any new strings describing it for translators
• added any new strings with date formatting to DateFormatsTest
• verified that any code or assets from external sources are properly credited in comments and/or in the about file.
• verified that any new UI elements use theme colors. UI Components Style guidelines