Is your feature request related to a problem? Please describe.
We currently cover java.sql.{Statement,PreparedStatement,CallableStatement} quite well, but we are missing instrumentation for Statement.executeBatch.

Describe the solution you'd like
At minimum a span:

• named with a constant value indicating it is a batch - e.g. "executeBatch", "Batch Statement(s)", or (Batch of statements)
• including a "placeholder" db.statement value indicating a batch - probably the same value as the span name
• that includes an attribute for how many statements were executed (the size of the return value) (e.g., db.statement.count)
• and with span status set appropriately if any returned values are EXECUTE_FAILED

For bonus points:

• Include a db.statement.error.count (or similar) attribute with the number of failed statements (return value needed to be iterated anyway for the span status)
• If all statements in the batch sanitize/normalize to the same string, set db.statement to that value. This would entail instrumenting addBatch and clearBatch and may not be worth the extra overhead. I'd lean towards "don't build this" based on previous experience with instrumenting this API, since batches of "mixed" sql still wouldn't have a better representation anyway.

Describe alternatives you've considered
None; this is an odd blind spot in the existing instrumentation, and admittedly a bit of a corner case in the API anyway.

Additional context
N/A.