extension: support follow cursor and sorting in package outline

[aviralgarg05]

Package Outline now supports follow cursor, sort by name, and sort by
position, matching the controls available in Outline.

This change switches the Package Outline view to a TreeView so the active
symbol can be revealed as the cursor moves. It also adds view actions for
follow cursor and both sort modes, and keeps symbol ordering stable by
name or source position.

The cursor matching logic also handles receiver methods returned by
gopls.package_symbols, where methods may be grouped under a type without
being nested inside that type's source range.

Fixes #3998

[gopherbot]

This PR (HEAD: 4f62268) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/vscode-go/+/761181.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Gopher Robot:

Patch Set 1:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Aviral Garg:

Patch Set 1:

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Madeline Kalil:

Patch Set 2: Commit-Queue+1

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 2:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2026-04-09T20:56:51Z","revision":"118fef909d333f56035f8cfda19c6703413f2c20"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Madeline Kalil:

Patch Set 2: -Commit-Queue

(Performed by <GERRIT_ACCOUNT_60063> on behalf of <GERRIT_ACCOUNT_3771561>)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 2:

This CL has failed the run. Reason:

Tryjob golang/try/x_vscode-go-go1.25-linux-amd64_docker has failed with summary (view all results):

---

• go on release-branch.go1.25 (commit 7076e01) / vscode-go on master (change 761181)

To reproduce, try gomote repro 8684965782592232513.

Additional links for debugging:

• test github.com/golang/vscode-go module output

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 2: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Madeline Kalil:

Patch Set 2:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 74db76a) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/vscode-go/+/761181.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Aviral Garg:

Patch Set 2:

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Madeline Kalil:

Patch Set 3:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 6291440) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/vscode-go/+/761181.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Aviral Garg:

Patch Set 4:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Madeline Kalil:

Patch Set 4:

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Madeline Kalil:

Patch Set 4: Code-Review+2 Commit-Queue+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 4:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2026-04-14T20:16:25Z","revision":"c1e271a9fbc51c624c1aba78a15b116e6f667e79"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Madeline Kalil:

Patch Set 4: -Commit-Queue

(Performed by <GERRIT_ACCOUNT_60063> on behalf of <GERRIT_ACCOUNT_3771561>)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 4:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 4: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 6f9c67f) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/vscode-go/+/761181.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Aviral Garg:

Patch Set 5:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Madeline Kalil:

Patch Set 5: Code-Review+2

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Madeline Kalil:

Patch Set 5: Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 5:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2026-04-27T15:13:32Z","revision":"faa9cd45884a69be44bb80c226e81177425626fc"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Madeline Kalil:

Patch Set 5: -Commit-Queue

(Performed by <GERRIT_ACCOUNT_60063> on behalf of <GERRIT_ACCOUNT_3771561>)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 5:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 5: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Carlos Amedee:

Patch Set 5: Code-Review+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/761181.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR is being closed because golang.org/cl/761181 has been merged.