Reckless UI features

[endothermicdev]

[!IMPORTANT]

25.12 FREEZE October 27th: Non-bugfix PRs not ready by this date will wait for 26.03.

RC1 is scheduled on November 10th

The final release is scheduled for December 1st.

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:

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

Addresses several issues raised in #8439. Still working on a few of them.

[endothermicdev]

Rebased and updated reckless rpc to handle single argument reckless commands (the new listconfig, listavailable, listinstalled) and handle json objects in the result (listconfig output.)

[ShahanaFarooqui]

@endothermicdev I am listing our last discussion point here too for posterity & completeness:

15. Lightning CLI Argument Parsing Conflicts With Reckless From Receiving Common Flags

lightning-cli intercepts certain arguments before they can be passed to the reckless plugin, preventing users from accessing reckless-specific information. Affected arguments:

--help
--version
--conf

[ShahanaFarooqui]

14. Clear Old Reckless Configurations [UPDATE]: After reconsideration, this seems like a low-priority UI feature. Users should explicitly choose to remove plugins individually. A full factory-reset approach may be premature for the UI.

@endothermicdev Apologies for the earlier confusion and for not documenting this requirement more clearly. What I actually intended was a way to uninstall a plugin when the Core Lightning node cannot start because that plugin is causing a failure.

This does not need to be available through RPC, since the goal is to provide a recovery mechanism only when the CLN node is unable to start normally. This is mainly a safety and recovery feature rather than a user-facing management option.

For example, if I install the summary plugin, then prometheus, and later the backup plugin, and the backup plugin prevents the lightning node from starting, I would like the reckless plugin to be able to:

• uninstall the backup plugin,
• remove its configuration entries, and
• restart the Core Lightning node successfully.