cln-grpc, clnrest: workaround for logging before shutdown

[daywalker90]

Changelog-Fixed: cln-grpc and clnrest errors that cause them to stop will now log

Important

25.02 FREEZE JANUARY 31ST: Non-bugfix PRs not ready by this date will wait for 25.05.

Checklist

Before submitting the PR, ensure the following tasks are completed. If an item is not applicable to your PR, please mark it as checked:

• The changelog has been updated in the relevant commit(s) according to the guidelines.
• Tests have been added or modified to reflect the changes.
• Documentation has been reviewed and updated as needed.
• Related issues have been listed and linked, including any that this PR closes.

I consider this a bug fix pr for 25.02

[endothermicdev]

I don't think this failure was related to the PR, but as it's dealing with cln-rest, it's slightly suspicious. Let's allow a little more time on that test under valgrind.

[daywalker90]

Yeah i cant reproduce that locally, dont know what to do about it

[endothermicdev]

I tried it with the socket connection timeout set to 0.5s versus the default of 1 and it failed every time (when running under valgrind.) If we're that close, we may as well bump up the tolerance a bit. Under normal testing everything is snappy and I don't see any failures.

[daywalker90]

If that is the problem then from my experience the github ci is so slow that you need to up that number to 10 or something^^

[rustyrussell]

taskset -c 1 can sometimes slow your own machine down to GH speeds :)

Also see #8090

[endothermicdev]

Rebasing this onto master (don't mix Valgrind & Rust.)