Revisit historical TX handling

[maxtropets]

We've had some issues and long-lived bugs recently, for instance #7755

Historical cache arch needs revisiting. Also, some dumping some related things.

• Messy receipt population logic, we should do smth about that
• Historical adapter populates endorsements AND COSE endorsements unconditionally, maybe it shouldn't? Maybe we should serve them on demand? COSE endorsements are quick because of prefetching done in Prefetch COSE endorsements of previous identities #7518 , but regular ones are still fetched in the loop
• To top the previous off, regular endorsements are loaded one-per-poke on average, so needs poking 10x for pre-10-DR receipt? It's odd, and isn't good for SCITT scenarios maybe, which we maybe need to focus on.
• With regards to the endorsement, we may serve them separately via a dedicated endpoint? (mentioned in Create a dedicated endpoint for COSE service identity endorsement verification #6560)