chore: add print_stdout/print_stderr lints to workspace level

[oleonardolima]

potentially fixes #1362

Description

It adds both print_stdout and print_stderr deny level lints on workspace level, but it does allow it on test fns through clippy.toml settings, and explicitly allow it on example code.

Notes to the reviewers

It currently has the setting allowing it on test fns, but open for discussion below.

Changelog notice

• Add both print_stdout and print_stderr deny level lints on workspace level

Checklists

All Submissions:

• I've signed all my commits
• I followed the contribution guidelines
• I ran cargo fmt and cargo clippy before committing

New Features:

• I've added tests for the new feature
• I've added docs for the new feature

[notmandatory]

This looks like the right way to prevent prints from getting into the code. But do we even want to allow them on tests? The only place I think they should be allowed is in the examples.

[oleonardolima]

This looks like the right way to prevent prints from getting into the code. But do we even want to allow them on tests? The only place I think they should be allowed is in the examples.

I'm fine with it either way, but I don't see a problem with allowing it for tests.

[evanlinjin]

Concept ACK

Just needs a rebase! We got rid of the bdk_persist crate.

[notmandatory]

Thanks for cleaning this up, I'd just like to remove the println!() from all tests to make cargo test output more readable. If someone really needs to print stuff while debugging tests they can remove or comment out the print lines.

[notmandatory]

ACK e063ad8

Looks great! much easier to read through the test output with out all the println noise.