Allow unknown config options in client

[benthecarman]

Bug accidentally introduced in #216, now tests will catch

We purposely don't parse the entire the config in the client, only the things releveant to the client. When we added the denys in e5eccc1 we now will fail with a normal config because our cli will throw an error for the config options we don't parse in the client.

[ldk-reviews-bot]

👋 Thanks for assigning @tankyleo as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[tankyleo]

Bug accidentally introduced in #216, now tests will catch

We purposely don't parse the entire the config in the client, only the things releveant to the client. When we added the denys in e5eccc1 we now will fail with a normal config because our cli will throw an error for the config options we don't parse in the client.

Ah my bad, I was still in the old world where we have ldk-server-config.toml !

So I thought clients just had a separate configuration file called config.toml. I did not understand config.toml is now also the config file for ldk-server :)