Handle Arbitrary and Blind SigningInput Types in Sign Data Flow

We are currently handling displaying the transaction summary part of a signing inputs object correctly. Now we need to handle displaying arbitrary and blind types of signing inputs correctly.

The issue mentions handling 'arbitrary and blind types of signing inputs' in a 'sign data flow' but provides no code, file names, or specific behavior to change. Start by searching the repository for 'signing inputs', 'transaction summary', and related terms to understand the current implementation. Look for existing display logic and tests to see how different input types are currently handled. Determine what 'correctly' means for arbitrary and blind types by examining the project's documentation or asking the maintainers.

Vom Indexierungsmodell aus dem Issue-Text verfasst.