Fix typos in comments and docs

[fematarazzo]

Fix several doubled words and misspellings found across comments, test files, and documentation

• go/types/objectpath: "ouf the the" → "out of the"
• gopls/internal/cache: "the the" → "the"
• gopls/internal/cmd/codeaction: "and and" → "and"
• gopls/internal/analysis/yield: "to to" → "to"
• gopls/doc/features/transformation: "and and" → "and"
• go/analysis/internal/checker: "with with" → "with"
• gopls/internal/filewatcher: "with with" → "with"
• go/analysis/passes/printf: "excepted" → "expected"
• gopls/internal/test/integration/codelens: "nonexistant" → "nonexistent"

[gopherbot]

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

Please visit Gerrit at https://go-review.googlesource.com/c/tools/+/772600.

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/772600.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alan Donovan:

Patch Set 1: Auto-Submit+1 Code-Review+2 Commit-Queue+1

(1 comment)

---

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

[gopherbot]

Message from Go LUCI:

Patch Set 1:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2026-04-30T21:58:22Z","revision":"82f021d31dfbe4128ee6e8fbb8a6f14298a02fce"}

---

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

[gopherbot]

Message from Alan Donovan:

Patch Set 1: -Commit-Queue

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

---

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

[gopherbot]

Message from Go LUCI:

Patch Set 1:

This CL has failed the run. Reason:

Tryjob golang/try/x_tools-go1.26-linux-amd64 has failed with summary (view all results):

---

• go on release-branch.go1.26 (commit 0bec633) / tools on master (change 772600)

To reproduce, try gomote repro 8683059375952834961.

Additional links for debugging:

• test golang.org/x/tools/gopls module output

---

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

[gopherbot]

Message from Go LUCI:

Patch Set 1: LUCI-TryBot-Result-1

---

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