Fix broken meta resource paths on blog subpages

[remo-lab]

Summary

This PR fixes several broken resource paths in the blog Meta component that caused web manifest, favicon, and browser configuration files to resolve incorrectly on blog subpages. The issue resulted in 404s on post, tag, and author pages and affected SEO, PWA support, and favicon loading.

Problem

The blog is served under the /blog base path, but some meta resources in components/meta.tsx were defined using relative URLs (e.g. blog/favicon/...). On nested routes, these paths were resolved relative to the current page, leading to incorrect URLs such as:

• /blog/blog/favicon/...
• /blog/technology/some-post/blog/favicon/...
  As a result, the web manifest and browser configuration files returned 404s, and some icon references pointed to non-existent assets.

Fix

This change updates the affected meta resource paths to use absolute URLs under /blog and cleans up invalid references:

• Updated the web manifest and browserconfig paths to /blog/favicon/...
• Fixed icon references to use the existing Group.png asset with the correct file extension
• Removed the RSS feed link, as feed.xml does not exist in the project
• These changes align the meta configuration with other correctly defined paths in the same file.

screenshot from blog website:

screenshot from local server:

Impact

• Eliminates 404 errors for manifest and browser configuration files on all blog subpages.
• Restores correct favicon and shortcut icon loading.
• Improves SEO and PWA compatibility on mobile and desktop.
• Removes a broken RSS feed reference.

How to verify

• Open any blog post page (e.g. /blog/community/...)
• Open DevTools → Network and refresh the page
• Confirm the web manifest and icon resources load successfully without 404s

[remo-lab]

Hi @Achanandhi-M @amaan-bhati ,
This PR fixes broken meta resource paths on blog subpages that were causing the web manifest and related resources to return 404s.Whenever you get time, I’d really appreciate a review.