doc: write release notes for Go 1.23

[dmitshur]

This is the tracking issue for writing the Go 1.23 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.23.

This is the first release to use the improved release note process being implemented in #64169. Also see a corresponding golang-dev thread. (CC @jba.)

Up until the the end of the development cycle (end of May), release note fragments are added inside the doc/next directory in the main Go repo. This is documented in the "For developers" section of doc/README.md:

https://go.googlesource.com/go/+/HEAD/doc/#for-developers

At the end of the development cycle, the doc/next files will be merged into a single go1.23.md file, and all remaining edits will take place in it. This merge will be handled as part of the Go release process.

The previous issue was #61422.

[gopherbot]

Change https://go.dev/cl/563856 mentions this issue: doc/go1.23: document macOS requirements

[gopherbot]

Change https://go.dev/cl/568755 mentions this issue: doc/go1.23: document database/sql wrap errors

[jfrech]

I think 3c78ace's changes are worth mentioning.

[ianlancetaylor]

@jfrech Thanks, but the release notes are for changes that users need to know because they are new or because they will affect the way that programs work. We don't usually mention specific optimizations in the release notes, unless they affect the great majority of Go programs.

[gopherbot]

Change https://go.dev/cl/587415 mentions this issue: doc/initial, doc/next: add draft notice to introduction

[gopherbot]

Change https://go.dev/cl/587436 mentions this issue: cmd/golangorg: add doc/next page to preview draft release notes