Refactor: Remove ImageLoader usages from Blaze

[kean]

This brings us one step closer to removing AlamofireImage and consolidating all the image management code in ImageDownloader and AsyncImageView.

My initial idea was to update the existing (deprecated) ImageLoader to use ImageDownloader, but after a quick search, I realized that there were only seven remaining places where it was used. So, I decided to remove ImageLoader usages instead.

Changes:

• Update Blaze cells to use AsyncImageView
• Fix an issue with Blaze campaigns in the Blaze screen being displayed with a gray background (not sure why it was there in the first place, clearly an issue)

Before / After

To test:

Regression Notes

1. Potential unintended areas of impact

2. What I did to test those areas of impact (or what existing automated tests I relied on)

3. What automated tests I added (or what prevented me from doing so)

PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding unit tests for my changes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Testing checklist:

• WordPress.com sites and self-hosted Jetpack sites.
• Portrait and landscape orientations.
• Light and dark modes.
• Fonts: Larger, smaller and bold text.
• High contrast.
• VoiceOver.
• Languages with large words or with letters/accents not frequently used in English.
• Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
• iPhone and iPad.
• Multi-tasking: Split view and Slide over. (iPad)

[dangermattic]

	1 Warning
⚠️	PR is not assigned to a milestone.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.

	App Name	WordPress Alpha
	Configuration	Release-Alpha
	Build Number	pr23891-73f82b3
	Version	25.5
	Bundle ID	org.wordpress.alpha
	Commit	73f82b3
	App Center Build	WPiOS - One-Offs #11170

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

[crazytonyli]

I feel like I have commented about this before... I apologize if you have already answered this question... 😅

I think it's good to express "the given size (in pixels)" in code. Like sizeInPixel: CGSize, or creating a struct PixelSize { pixelWidth, pixelHeight } type.

It's easy to miss documentation, but it's very hard to miss if you have to write "pixel" in code.

[kean]

Yes. I already attempted it once by adding an ImageSize struct, but then realized the name was already taken – ugh! I added a note to try it again later 😄

PixelSize sounds. I can introduce it in a separate PR. It could also have a convenience initializer that takes points and multiplies by the display scale.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.

	App Name	Jetpack Alpha
	Configuration	Release-Alpha
	Build Number	pr23891-73f82b3
	Version	25.5
	Bundle ID	com.jetpack.alpha
	Commit	73f82b3
	App Center Build	jetpack-installable-builds #10208

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.