Add Allure reporting for Diesel queries

[baev]

Context

allure-diesel lets Diesel users capture database activity in Allure reports without changing individual query call sites. Add it as a dev dependency, then either attach instrumentation to a specific connection or install it globally for connections created by the code under test:

conn.set_instrumentation(allure_diesel::AllureInstrumentation::new());

allure_diesel::install_default()?;

The integration can also be tuned for different reporting needs. For example, users can disable transaction grouping, include connection events, omit full SQL attachments, or shorten long SQL step names:

let options = CaptureOptions::default()
    .without_transactions()
    .with_connection_events()
    .without_sql_attachment()
    .with_max_sql_preview(256);

let instrumentation = AllureInstrumentation::with_options(options);

In the report, each executed statement appears as an ordered step with the rendered SQL attached as query.sql. Transactions are grouped as nested transaction steps, so a successful flow looks like transaction (depth 1) containing BEGIN, insert into users ..., and COMMIT; failed queries, failed commits, and failed transaction starts are marked as failed steps with the Diesel error message.

Checklist

• Sign Allure CLA
• Provide unit tests

[github-actions]

Allure Report Summary

	Name	Duration	Stats	New	Flaky	Retry	Report
	Allure Rust – Pull request #21	26m 44s	222	0	0	0	View