[Feature Request]: add end_epoch to output of singularity deal list

[brianeggert]

What is the problem you're trying to solve?

Currently, the deals table in the local singularity.db contains both start_epoch and end_epoch for each deal, and I believe it uses end_epoch to continue to display expired deals, but it does not include it in the output of singularity deal list. It would be useful for tracking expired and expiring deals.

$ ./singularity deal list --provider f02639429 --state expired | head -n 2
2026-02-06T10:32:43.797-0600	INFO	database	database/connstring_cgo.go:35	Opening postgres database
DealID    State    Provider   PieceCID                                                          PieceSize    StartEpoch  Price  Verified  ClientID   
74721555  expired  f02639429  baga6ea4seaqj5cfd6oi3ahpasvzqs5wlugw3m4h4gg4s43zbg5lfbhrhemgcqkq  34359738368  3718033     0      true      f02208630  

singularity=> SELECT start_epoch, end_epoch FROM deals WHERE deal_id = 74721555;
 start_epoch | end_epoch 
-------------+-----------
     3718033 |   5258833
(1 row)

Describe the workaround you currently have

The only workaround I have is to run the filtered deal list against lotus state get-deal with a python script.

Describe the feature you'd like

I would like singularity to add the end_epoch to the stdout of deal list