`opentelemetry-instrumentation-mysqlclient`: expose `capture_parameters`

Part of #4787 (global db.query.parameter.<key> tracking issue).

Background

mysqlclient (MySQLdb) builds on the dbapi base, so once the dbapi sub-issue
lands it already emits db.query.parameter.<key> correctly — but only when
capture_parameters=True. The instrumentor never exposes that option, so users
have no way to enable parameter capture.

psycopg2 already exposes capture_parameters and is the reference
implementation.

What to do

Thread a capture_parameters option through the instrumentor, mirroring
psycopg2:

• In _instrument, read capture_parameters = kwargs.get("capture_parameters", False)
  and pass it to dbapi.wrap_connect(...).
• In instrument_connection, add a capture_parameters parameter and pass it
  to dbapi.instrument_connection(...).
• Document the option in the module docstring.

No parameter-formatting logic lives here — it all comes from the dbapi base.

Acceptance criteria

• instrument(capture_parameters=True) and
  instrument_connection(conn, capture_parameters=True) both enable capture.
• With capture enabled, spans carry db.query.parameter.<key> under the new
  semconv and db.statement.parameters under the old semconv (via the base).
• Default remains no parameter capture.

Tests

• Verify capture_parameters is forwarded to the dbapi layer for both entry
  points.
• Verify db.query.parameter.<key> appears under the new semconv when enabled.

Compare the psycopg2 instrumentor's capture_parameters handling, then inspect the mysqlclient instrumentor's _instrument and instrument_connection entry points. Confirm the option reaches the dbapi layer for both paths, verify the new db.query.parameter. attribute when enabled, and ensure the default remains disabled.