Log Message:
gopls: update to 0.14.0

This release includes initial support for the "inline call to function"
refactoring, as well as a few other smaller features. It also includes several
bug fixes, notably a fix for a performance regression in completion that may be
significant in some environments.

The release also contains support for opt-in telemetry. If you want, you can
enable the periodic uploading of telemetry data, including gopls stack traces
and metrics, but never your source code, to telemetry.go.dev. See below for
details.

New features
------------

- Refactoring: inline call to function
- Refactoring: removing unused parameters
- Improved support for go:embed directives, including hover and
  jump-to-definition

New analyses
------------

This release include three new static analyses, all of which are enabled by
default.

"appends": reports calls to append that pass no values to be appended \ 
to the
slice.

"defers": checks for common mistakes in defer statements.

"slog": checks for invalid structured logging calls.

Opt-in telemetry
----------------

This is the first gopls release to include opt-in transparent telemetry.
Telemetry uploading is off by default, and can be enabled with the following
command:

go run golang.org/x/telemetry/cmd/gotelemetry@latest on

After telemetry is enabled, gopls will periodically upload metrics and stack
traces to telemetry.go.dev. If we get enough adoption, this data can
significantly advance the pace of gopls development and help us meet a higher
standard of reliability. For example:

- Even with semi-automated crash reports in VS Code, we've seen several
  crashers go unreported for weeks or months.
- Even with a suite of benchmarks, some performance regressions don't show up
  in our benchmark environment (such as the completion bug mentioned below!).
- Even with lots of great ideas for how to improve gopls, we have limited
  resources. Telemetry can help us identify which new features are most
  important, and which existing features aren't being used or aren't working
  well.

These are just a few ways that telemetry can improve gopls. The telemetry blog
post series contains many more.

Go telemetry is designed to be transparent and privacy-preserving. If you have
concerns about enabling telemetry, you can learn more at
https://telemetry.go.dev/privacy.