Expose a `_test_utils` feature to expose integration test helpers

[DanGould]

Higher layer payjoin implementations like payjoin-ffi and payjoin-flutter and the bindings they produce would make use of a _test_utils feature like rust-lightning has. The _ prefix prevents it from being a listed feature in documentation by default.

This should expose:

• BitcoinD and wallet setup
• payjoin-directory setup and teardown
• ohttp-relay setup and teardown

(^ closed by ##484)

• including ephemeral Redis containers

Then, the higher level crates can create bindings to make these available in all languages we bind to for easy test duplication downstream.

[spacebear21]

To do this more cleanly, i guess would suggest introducing some kind of TestServices struct, make init_directory into something that constructs that (combining with relay initialization i suppose), and endow it with informational getters for e.g. the port/host numbers, as well as the owner of the Container/docker CLI structs that need to remain alive?

#421 should probably be addressed as part of such cleanup as well

Originally posted by @nothingmuch in #388 (comment)

[spacebear21]

Redis component closed by #507