Updated path in README sync automation

[mikeromard]

Description

This PR is to update the README sync automation to account for the new paths introduced in the user-docs repo with the new site architecture. The source file is moving from docs/developer-tools/snyk-ide-plugins-and-extensions/eclipse-plugin/README.md to developer-tools/snyk-ide-plugins-and-extensions/eclipse-plugin/README.md on May 28.

Checklist

• Read and understood the Code of Conduct and Contributing Guidelines.
• Tests added and all succeed
• Linted
• CHANGELOG.md updated
• README.md updated, if user-facing

Screenshots / GIFs

Visuals that may help the reviewer. Please add screenshots for any UI change. GIFs are most welcome!

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[CLAassistant]

All committers have signed the CLA.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Incorrect Path Depth 🟠 [major] The sed search pattern ../../../.gitbook/assets/ is incorrect for the new directory structure. According to the PR description, the file moved from docs/developer-tools/snyk-ide-plugins-and-extensions/eclipse-plugin/README.md to developer-tools/snyk-ide-plugins-and-extensions/eclipse-plugin/README.md. This move reduces the directory depth by one level. If the assets are now in developer-tools/.gitbook/assets/ (as implied by the replacement URL), the relative path in the source markdown is now ../../.gitbook/assets/. The current regex will fail to find any matches, causing image links in the synchronized README to remain as relative paths that won't resolve on GitHub. -e "s|../../../.gitbook/assets/|https://github.com/snyk/user-docs/raw/HEAD/developer-tools/.gitbook/assets/|g" \

📚 Repository Context Analyzed This review considered 4 relevant code sections from 4 files (average relevance: 0.72) CONTRIBUTING.md (lines 1-95) RELEASE.md (lines 1-86) CHANGELOG.md (lines 1-4) README.md (lines 1-48)