fix: call wait_chain members positionally

[codechrl]

wait_chain.__call__ calls each member strategy as
wait_func(retry_state=retry_state). WaitBaseT is
Callable[[RetryCallState], float | int], so a plain callable takes the
state positionally and need not name its parameter retry_state. Such a
member raises TypeError: <lambda>() got an unexpected keyword argument 'retry_state'.

The effect is that a plain callable cannot be used inside a wait_chain,
which is the combinator for phase-based backoff. The same callable works as
wait=, because BaseRetrying._run_wait calls it positionally. The failure
needs both a wait_chain and an attempt that retries, so it surfaces at the
first retry rather than at construction.

The fix passes the state positionally and widens wait_chain(*strategies)
from wait_base to WaitBaseT. #694 made both changes for wait_combine.
tenacity/asyncio does not override wait_chain.

A/B verified against 26f719d: test_wait_chain_passes_state_positionally
fails with the TypeError above before the change and passes after.
Reverting the tenacity/wait.py hunk alone puts it back to failing. Release
note added under releasenotes/notes/.