[Bug]: Replace <img> tags with next/image to satisfy Next.js lint warnings

Summary

The project currently triggers @next/next/no-img-element lint warnings because raw <img> tags are used in a few components. These should be reviewed and replaced with Image from next/image where appropriate.

Page

N/A

Details

Running the lint command reports @next/next/no-img-element warnings in the following files:

• src/components/Layout/HomeContent.js
• src/components/MDX/MDXComponents.tsx

Warning count:

• HomeContent.js: 4 occurrences
• MDXComponents.tsx: 3 occurrences

Using raw <img> elements in a Next.js app bypasses built-in image optimization and triggers lint warnings. Replacing them with Image from next/image would align the codebase with Next.js best practices.

Note:
Some usages, especially in MDX-related rendering, may require additional handling and should be updated carefully rather than through a blind replacement.

檢查 src/components/Layout/HomeContent.js 和 src/components/MDX/MDXComponents.tsx，然後執行 lint 命令以檢視回報的七處問題。將適合的原始 img 元素替換為 next/image，同時仔細處理 MDX 渲染，並確認 @next/next/no-img-element 警告已解決。