sync: add track_caller to public APIs

[hds]

Motivation

When a user of tokio calls a function that panics when misused (e.g. calling
Mutex::blocking_lock() from within a tokio runtime) then the user currently
sees the line number of the panic call inside tokio. It would be more informative
for the user to see the place where they called the panicking function.

It is still possible for the user to see the full stack trace by setting the
environment variable RUST_BACKLOG=1, so no useful information is
hidden.

This change is the 7th in a series towards closing #4413 (starting with #4772),
this change is for the sync functions in the main tokio crate.

Solution

Functions that may panic can be annotated with #[track_caller] so that
in the event of a panic, the function where the user called the
panicking function is shown instead of the file and line within Tokio
source.

This change adds #[track_caller] to all the public APIs in the sync
module of the tokio crate where the documentation describes how the
function may panic due to incorrect context or inputs.

In cases where #[track_caller] does not work, it has been left out.
For example, it currently does not work on async functions, blocks, or
closures. So any call stack that passes through one of these before
reaching the actual panic is not able to show the calling site outside
of tokio as the panic location.

The following functions have call stacks that pass through closures:

• sync::watch::Sender::send_modify
• sync::watch::Sender::send_if_modified

Additionally, in the above functions it is a panic inside the supplied
closure which causes the function to panic, and so showing the location
of the panic itself is desirable.

The following functions are async:

• sync::mpsc::bounded::Sender::send_timeout

Tests are included to cover each potentially panicking function.

Refs: #4413

[Noah-Kennedy]

wait what, double approve lol