Audit and update redirect rules to use 301s and streamline redirect management

Following the test in #861 (closed), we confirmed that using a 301 (permanent) redirect allows Google to update its search index and reflect the destination page's metadata.

With this issue, I'd like us to review and update our existing redirect rules to use 301 status codes where appropriate — particularly for completed site migrations — to improve SEO. The current use of 302 (temporary) redirects may limit how effectively these pages are indexed.

Note: 302 redirects are still useful for cases where the destination URL might change in the future or when behavior is still being validated.

Current Redirect Configuration

Most redirect rules are currently defined in:

Recommendation

Update applicable redirects to use 301 instead of 302, especially for completed site migrations.
Continue using 302 where redirects are still under review or the destination may change.
Consider migrating project-specific redirects such as https://gitlab.eclipse.org/eclipsefdn/it/internal/infra/configuration-management/puppet-modules/-/blob/main/nginx/files/etc/nginx/conf.d/redirects/www_redirects?ref_type=heads#L87 from the edge proxy config to the eclipse.org Hugo project, especially where the content is already served by Hugo pods.

This would help streamline redirect management and simplify the edge reverse proxy configuration — which should be a long-term goal for us.

Next Steps

Audit current redirects in both locations.
Identify which redirects should be updated to 301.
Propose or move applicable redirects to the Hugo project config where appropriate.

/cc @etory @droy