clnrest: dynamic content-type and accept headers

[ShahanaFarooqui]

Make the type of REST responses configurable via Accept header, so that applications can consume the response without writing wrappers/interceptors; if they do not consume default application/json type.

And

Make the payload of REST request configurable via Content-Type header, so that the server can consume the payload in different formats and convert it into json before passing it to the node.

Request Header Meaning:
-H Accept -> "I prefer to receive responses in {} format"
-H Content-Type -> "The data I'm sending is in {} format"

[gudnuf]

I am working on adding properties http_path and http_method to a plugin command's manifest entry, this will allow plugins to set specific REST mappings for their RPCs rather than being fixed at /v1/<command_name>. Seems like a good place to include the content-type of the response, then this data can be handled by CLNRest to create dynamic routes

[BitcoinJiuJitsu]

Open CLN bounty on this:
https://community.corelightning.org/c/cln-bounties/7164-clnrest-configurable-content-type-header