Replace concatenated localize calls with single localize for gutter indicator menu

[Copilot]

Localized strings should not be concatenated with hardcoded separators. Different languages may use different separators, word order, or phrasing entirely.

Before:

title: `${localize('goto', "Go To")} / ${localize('accept', "Accept")}`

After:

title: localize('gotoAndAccept', "Go To / Accept")

This allows translators to provide the appropriate phrasing for their language rather than being forced to use the English "Foo / Bar" pattern.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>debt - don't do nls concat</issue_title>
<issue_description>Found this ⬇️. It's better to have a single nls/localize string and not hardcode the /-character. We don't know if all languages use the "Foo / Bar"

vscode/src/vs/editor/contrib/inlineCompletions/browser/view/inlineEdits/components/gutterIndicatorMenu.ts

Line 72 in 16ccd1a

title: `${localize('goto', "Go To")} / ${localize('accept', "Accept")}`,

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes debt - don't do nls concat #286571

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

Reworks the gutter indicator menu label localization to avoid concatenating multiple localize() calls with a hardcoded separator, allowing translators to control phrasing and separators appropriately.

Changes:

• Replaced a template-literal concatenation of two localized strings ("Go To" and "Accept") with a single localized string ("Go To / Accept").