feat!: remove the ability to send completely raw bytes via grpc (#7117)

Description
---
Changes the transfer command, that if you provide the raw bytes, it puts
it into the open format.
This does change legacy behaviour, but most people who use this are not
aware that the bytes if provided in raw from need to contain some other
details as well.

By providing raw data to the wallet it thinks its i nthe correct form,
but its not and this leads to weird looking payment id's

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Transaction details now include comprehensive input and output
commitment data for enhanced transparency.
- Transaction responses in transfers and batch processes provide
enriched metadata for better insight.
- **Refactor**
- Improved payment ID construction during transfers for more precise
transaction identification.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: SWvheerden

applications/minotari_app_grpc/proto/wallet.proto

@@ -1151,6 +1151,7 @@ message TransferResult {
   uint64 transaction_id = 2;
   bool is_success = 3;
   string failure_message = 4;
+  TransactionInfo transaction_info = 5;
 }
 
 message ClaimShaAtomicSwapRequest{
@@ -1194,6 +1195,8 @@ message TransactionInfo {
   bytes raw_payment_id = 12;
   uint64 mined_in_block_height = 13;
   bytes user_payment_id = 14;
+  repeated bytes input_commitments = 15;
+  repeated bytes output_commitments = 16;
 }
 
 enum TransactionDirection {