feat(types): add new types for inputs/outputs and options

[storopoli]

These types are needed to finalize the migration of bitcoind-async-client to use corepc-types.

They are currently being used by Alpen Labs and Payjoin Dev Kit.

I put them in v29 for now, but let me know if we need to put them in previous versions.

[tcharding]

What are these types used for? By the client to do RPC calls? If so we don't want them in types I'm afraid.

[storopoli]

What are these types used for? By the client to do RPC calls? If so we don't want them in types I'm afraid.

Yes, so where should we put them?

[jamillambert]

I think they should go in /client/src/client_sync/vXX/mod.rs

[storopoli]

Ok closing this because my main use case was to implement in an async client and get rid of my custom types.

[tcharding]

These types should stay in your client.

[tcharding]

I think they should go in /client/src/client_sync/vXX/mod.rs

He isn't using our client.