Visibility of API calls and rate limiting headers in debug/trace would help troubleshooting

[davidsandilands]

Is your feature request related to a problem? Please describe.
Users of the LDCLI who find they are hitting rate limits often don't understand exactly why and don't have anything to troubleshoot off

Describe the solution you'd like
A way to have a trace which shows which api calls were made and the returned http headers with the rate limits

Describe alternatives you've considered
Beyond using the API directly I didn't think of any alternatives

Additional context
n/a

[mike-zorn]

I think we'll need to add some custom error handling for 429 status codes here. Then we can include the rate limit and when they should retry their request. Would that be enough information? Or is there other information that is needed to debug?