spymemcached: capture command arguments in db query text

Describe the bug

spymemcached instrumentation currently records operation name (e.g. get, set) but does not capture command arguments into statement/query attributes.
As a result, telemetry misses key command context compared to other cache/db instrumentations (e.g. redis clients).

Steps to reproduce

--

Expected behavior

For memcached commands, capture argument context into query text with sanitization, aligned with existing patterns used by other instrumentations:

• collect command-relevant args
• sanitize sensitive values (e.g. values -> ?)
• emit statement/query text attribute
  Example expectations:
• get my-key
• set my-key 3600 ?
• getBulk key1 key2

Actual behavior

• db.operation.name is present
• command argument context is missing from db.statement / db.query.text

Javaagent or library instrumentation version

2.27.0

Environment

JDK:
OS:

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

Start by locating the spymemcached instrumentation and comparing its command handling with the existing Redis instrumentation patterns referenced in the issue. Done means command-relevant arguments appear in the statement/query text, sensitive values are sanitized, and examples such as get, set, and getBulk produce the expected context.