runtime: use runtime.AddCleanup in the standard library

[cagedmantis]

AddCleanup has been added to the runtime (#67535). We should use runtime.AddCleanup instead of runtime.SetFinalizer in the standard library wherever it is possible.

Remaining instances of SetFinalizer (outside of runtime):

• crypto/internal/boring: no longer supported. No use in updating.
• crypto/tls: CL 664275
• go/parser/testdata: test only change. Not worth modifying.
• internal/types/testdata/check: test only change. Not worth modifying.
• internal/poll: CL 671441
• net: CL 638557 adds TODOs
• os/exec (Current code relies on object resurrection)
• reflect: test only change. Made easy modifications where possible CL 667595
• syscall/js (Current code relies on object resurrection)
• weak (intentionally used in test)

@mknyszek

[gabyhelp]

Related Issues

• runtime: deprecate SetFinalizer #70425

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[gopherbot]

Change https://go.dev/cl/638555 mentions this issue: os: use AddCleanup to close files

[gopherbot]

Change https://go.dev/cl/638557 mentions this issue: net: use runtime.AddCleanup instead of runtime.SetFinalizer

[gopherbot]

Change https://go.dev/cl/638556 mentions this issue: io: use runtime.AddCleanup instead of runtime.SetFinalizer

[gopherbot]

Change https://go.dev/cl/638578 mentions this issue: os: simplify process status

[gopherbot]

Change https://go.dev/cl/638576 mentions this issue: os: remove Process.mode field

[gopherbot]

Change https://go.dev/cl/638579 mentions this issue: os: use AddCleanup, not SetFinalizer, for Process

[gopherbot]

Change https://go.dev/cl/638575 mentions this issue: os: separate Process.handle into a separate memory allocation

[gopherbot]

Change https://go.dev/cl/638577 mentions this issue: os: don't store reference count in Process.state