This commit introduces a new extension to Dry::Operation that allows
operations to be wrapped in ActiveRecord transactions. This is useful
for ensuring atomicity of operations that involve multiple steps that
need to be rolled back in case of failure. The extension provides a
`transaction` method that can be used to wrap steps in a transaction.
The transaction will be rolled back if any of the steps return a
`Dry::Monads::Result::Failure`.

The extension also supports specifying a custom ActiveRecord class to
initiate the transaction, which is useful when working with multiple
databases.

- Fix information in doc.
- Improve tests to get rid of `let!` and more reliable way to call model
methods
- Prevent verbose messages of AR migrations. Cleanup db after tests

This commit enhances the ActiveRecord extension of the Dry::Operation
module to support additional options for the ActiveRecord transaction.
These options can be set as default for all transactions or overridden
at runtime. The changes include updates to the method signatures and
the addition of new tests to verify the functionality.

The line exceeds 100 characters. Shorter param names are still good
enough.

Move the yardoc comment block to the define_method block.
With the stand-alone `@!method` block, yard always generate warning of
unknown parameter name.