chore: Standardize pipeline optimization service name

[bebosudo]

Standardize the name of the "Pipeline Optimization" service; remove "resource" from the name; explain that groundswell is used internally; and add it to tags.

[netlify]

✅ Deploy Preview for seqera-docs ready!

Name	Link
🔨 Latest commit	a559142
🔍 Latest deploy log	https://app.netlify.com/projects/seqera-docs/deploys/6984ec608e1b200008822db0
😎 Deploy Preview	https://deploy-preview-1106--seqera-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

📝 Editorial Review with Inline Suggestions

I've reviewed the documentation and found some areas for improvement. Click Commit suggestion on each inline comment to apply the fix.

Review powered by Claude Code editorial agents

[github-actions]

📋 Additional Issues Found in Unchanged Lines

I found 27 additional issues in unchanged lines of the files you modified. While these aren't part of your PR changes, consider fixing them in a follow-up:

platform-cloud/docs/pipeline-optimization/overview.md

• Line 98: Future tense usage - "will listen on" should be present tense
• Line 102: Future tense usage - "will listen on" and "will route" should be present tense

platform-enterprise_docs/enterprise/platform-docker-compose.md

• Line 98: Future tense usage - "will soon deprecate" should be present tense
• Line 100: Future tense usage - "will listen on" and "will route" should be present tense

platform-enterprise_versioned_docs/version-25.1/enterprise/platform-docker-compose.md

• Line 98: Future tense usage - "will soon deprecate" should be present tense
• Line 100: Future tense usage - "will listen on" and "will route" should be present tense

platform-enterprise_versioned_docs/version-25.2/enterprise/platform-docker-compose.md

• Line 98: Future tense usage - "will soon deprecate" should be present tense
• Line 100: Future tense usage - "will listen on" and "will route" should be present tense

platform-enterprise_versioned_docs/version-25.3/enterprise/platform-docker-compose.md

• Line 98: Future tense usage - "will soon deprecate" should be present tense
• Line 100: Future tense usage - "will listen on" and "will route" should be present tense

platform-cloud/docs/pipeline-optimization/overview.md

• Line 24: Use backticks for UI elements (dropdown is a code/UI element)

platform-enterprise_docs/enterprise/groundswell-docker-compose.md

• Line 26: Use backticks for file names consistently
• Line 60: Use backticks for file names consistently

platform-enterprise_docs/enterprise/groundswell-kubernetes.md

• Line 42: Use backticks for ConfigMap name (Kubernetes resource name)

platform-enterprise_docs/pipeline-optimization/overview.md

• Line 24: Use backticks for UI elements (dropdown is a code/UI element)

platform-enterprise_versioned_docs/version-25.1/enterprise/groundswell-docker-compose.md

• Line 26: Use backticks for file names consistently
• Line 60: Use backticks for file names consistently

platform-enterprise_versioned_docs/version-25.1/enterprise/groundswell-kubernetes.md

• Line 42: Use backticks for ConfigMap name (Kubernetes resource name)

platform-enterprise_versioned_docs/version-25.1/pipeline-optimization/overview.md

• Line 24: Use backticks for UI elements (dropdown is a code/UI element)

platform-enterprise_versioned_docs/version-25.2/enterprise/groundswell-docker-compose.md

• Line 26: Use backticks for file names consistently
• Line 60: Use backticks for file names consistently

platform-enterprise_versioned_docs/version-25.2/enterprise/groundswell-kubernetes.md

• Line 42: Use backticks for ConfigMap name (Kubernetes resource name)

platform-enterprise_versioned_docs/version-25.2/pipeline-optimization/overview.md

• Line 24: Use backticks for UI elements (dropdown is a code/UI element)

platform-enterprise_versioned_docs/version-25.3/enterprise/groundswell-docker-compose.md

• Line 26: Use backticks for file names consistently
• Line 60: Use backticks for file names consistently

platform-enterprise_versioned_docs/version-25.3/enterprise/groundswell-kubernetes.md

• Line 42: Use backticks for ConfigMap name (Kubernetes resource name)

platform-enterprise_versioned_docs/version-25.3/pipeline-optimization/overview.md

• Line 24: Use backticks for UI elements (dropdown is a code/UI element)

---

💡 Tip: These issues are in code outside the PR diff. GitHub doesn't allow inline suggestions on unchanged lines.
Review powered by Claude Code editorial agents

[github-actions]

📝 Documentation Review Summary (PR type: content)

Check	Status
Terminology (Vale)	❓
Voice/Tone (AI)	✅ success
Terminology (AI)	✅ success

---

Review powered by Claude Code editorial agents

To apply suggestions:

• Click "Commit suggestion" on individual inline comments
• Select multiple suggestions and batch commit them together

[justinegeffen]

Some small editorial changes but otherwise looks good to me! Thank you!