gh-149306: Improve error messages in wave module to include the offending value

[htjworld]

Summary

Include the offending value in wave.Error messages raised by:

• Wave_read._read_fmt_chunk (parses WAV file header)
• Wave_write.setnchannels
• Wave_write.setsampwidth
• Wave_write.setframerate

Before:

wave.Error: bad # of channels
wave.Error: bad sample width
wave.Error: bad frame rate

After:

wave.Error: bad # of channels: 0
wave.Error: bad sample width: 0
wave.Error: bad frame rate: -1

Motivation

Wave_read: Values come from the WAV file header — they never appear
in the traceback. The error message is the only debugging clue.

Wave_write: When values originate from variables, configuration files,
or parsed data rather than literals, the traceback shows the call site but
not the value itself. For example, w.setframerate(config['rate']) raises
bad frame rate with no indication of what config['rate'] was.

This extends the clear-feedback approach introduced in gh-144976, which fixed
the validation order in setframerate to raise immediately at the point of
the mistake. Showing the offending value is the natural next step.

For setframerate, the original value (before int(round())) is shown rather
than the rounded result, so callers see exactly what they passed.

Precedent

• statistics: raise StatisticsError(f'No negative inputs allowed: {x!r}') (statistics: Fix geometric_mean() error message for negative inputs #149246)
• asyncio: raise ValueError(f'A Stream Socket was expected, got {sock!r}')

Notes

• Error type is unchanged; only the message text is refined.
• The bits/bytes unit ambiguity in bad sample width predates this PR and can be addressed separately.
• NaN/Inf handling in setframerate is pre-existing behaviour and out of scope here.

• Issue: Improve wave module error messages to include the offending value #149306