Describe the bug

Before commit e4f6345, this issue only occurs when storage is set to local or database.
Using S3 as storage avoids high memory usage because when S3 is used, the frontend loads images via external links (S3 presigned URLs), eliminating the need for additional processing by the memos instance itself.

However, e4f6345 also points the image URL to the memos instance when using S3 as storage, causing high memory usage and contradicting the original intent of using S3 to reduce workload.

In my case, I deployed memos using docker with memory limit and using S3 as storage.
Update to this commit caused the program to crash frequently.

Steps to reproduce

1. Update memos to commit e4f6345.
2. Open resource tab.
3. Program crashes due to memory limit.

The version of Memos you're using

v0.25.1

Screenshots or additional context

No response