x/tools/gopls: Analyze bug reported by telemetry

[adonovan]

This stack mmNRcw was reported by telemetry:

Analyze.266 is

				// Although this 'skip' operation is logically sound,
				// it is nonetheless surprising that its absence should
				// cause #60909 since none of the analyzers added for
				// requirements (e.g. ctrlflow, inspect, buildssa)
				// is capable of reporting diagnostics.
				if summary := root.summary.Actions[a.Name]; summary != nil {
					if n := len(summary.Diagnostics); n > 0 {
						bug.Reportf("Internal error: got %d unexpected diagnostics from analyzer %s. This analyzer was added only to fulfil the requirements of the requested set of analyzers, and it is not expected that such analyzers report diagnostics. Please report this in issue #60909.", n, a)
					}
				}

gopls/bug
golang.org/x/tools/gopls/internal/bug.report:35
golang.org/x/tools/gopls/internal/bug.Reportf:1
golang.org/x/tools/gopls/internal/lsp/cache.(*snapshot).Analyze:266
golang.org/x/tools/gopls/internal/lsp/source.Analyze:21
golang.org/x/tools/gopls/internal/lsp.(*Server).diagnosePkgs.func2:2
runtime.goexit:0

golang.org/x/tools/[email protected] go1.21.3 darwin/arm64 (4)
golang.org/x/tools/[email protected] go1.21.0 linux/amd64 (2)
golang.org/x/tools/[email protected] go1.21.1 darwin/arm64 (11)

Reported using golang.org/x/tools/gopls/internal/telemetry/cmd/stacks.

[adonovan]

This has not been observed in v0.15. I wonder whether it was inadvertently fixed.

[adonovan]

No reports in v0.15; presumed inadvertently fixed.