Clarify stance on corepc-client to be integration-test-only #507
Description
As far as I understood, Tobin's original stance was that he intended corepc-client to merely be for testing purposes only and didn't want to add/support any more features.
Hence the disclaimer in the README currently states:
If you require a JSON RPC client in production software it is expected you write your own and only use the corepc-types crate in your dependency graph. Feel free to copy/steal/plagiarise or otherwise enjoy yourself with anything in this repository - no attribution required.
This lead projects like BDK and Alpen to start working on their own client libraries (see https://github.com/bitcoindevkit/bdk-bitcoind-client and https://github.com/alpenlabs/bitcoind-async-client), and we (LDK) eventually would also need to switch to some async client based on corepc-types.
However, PRs like #505 / #506 seem like there is/will be ongoing development on corepc-client that even adds async support. So I just wanted to check in to see if that stance has changed by now?
(I personally of course still think that that sharing resources would be great to avoid redundant work for each dependent project individually.)