[feature]: `reversed` option in forwarding history endpoint

[LightningK0ala]

Is your feature request related to a problem? Please describe.
Inability to get forwarding history in reverse chronological order.

Describe the solution you'd like
A reversed option in the ForwardingHistory endpoint just like ListInvoices and ListPayments.

Describe alternatives you've considered
There are none.

Additional context
N/A

[Janmesh23]

Hi @LightningK0ala , I took a look at this and it seems the main issue is that ForwardingHistory currently returns results only in chronological order (oldest → newest), which makes it harder to access recent forwarding activity without additional client-side sorting.
A possible solution would be to add an optional reversed flag to the ForwardingHistoryRequest, similar to what already exists in ListInvoices and ListPayments. When this flag is set, the RPC would return results in reverse chronological order (newest → oldest), while preserving the current behavior as the default for backward compatibility.
From an implementation perspective, this would likely involve:
adding a reversed field to the RPC request,
passing this option through the router server to the forwarding log query,
and iterating over forwarding events in reverse order when requested, without changing the underlying storage format or schema.
This keeps the change small, avoids breaking existing clients, and makes the API behavior consistent with other list-style RPCs in lnd.
Happy to work on this if this direction sounds reasonable.