Audit plugin, log values used in prepared statements

This works with the new audit plugin. For example, executing

will log audit events with the following fields (not including the whole output here)

This should work for our new audit plugin. Added MTR test to make sure there is separate record with actual parameters values for each prepared statement execution.

Hi , thanks for submitting this request. In terms of logging actual queries you have available the Slow log or Performance Schema so you'll see the final input values there. The audit log isn't designed to replicate the Slow log, but rather provide an audit trail of activity within the database.

Prepared statements by design submit their first request without values to the MySQL server in order to evaluate the query execution plan that will be used on subsequent requests. This is something the client library applies and thus there isn't anything the MySQL server can do about it. I might be mistaken on how prepared statements work across audit log and Slow log, please share a reproducible test case if you see behaviour differently.

I'll move this also into the Percona Server queue so that the Development team can have a review. Thanks for your submission,