Filtering the Lovelace Asset Id within `runtimeLifecycle.payouts.available()`

[nhenin]

The first implementation of runtimeLifecycle.payouts.available() was naively considering all the asset Ids within the connected wallet as "Potential" Role tokens.

This issue is about considering all the asset Ids within the connected wallet as "Potential" Role tokens expected the Lovelace one.

Discussed in https://github.com/input-output-hk/marlowe-ts-sdk/discussions/151

^{Originally posted by albert-kevin December 28, 2023} roleToken for example policyId.policyName for example: 10137ccc04dc177e9af17c7800f3fbe86855c63d22fad293b8d98695.Party1 and somebody created a contract with empty policyId and empty name

             (Role "")
             (Role "")
             (Token "" "")
             https://preview.marlowescan.com/contractView?tab=state&contractId=71f42745070424400d0c8fb3d5df8302e53dec10d2c525c038d21c298bd14cdf%231
             
             when you use the SDK code runtimeLifecycle.payouts.available()
             it searches for both your own wallet tokens and empty tokens... but the empty tokens are not from your wallet, so what about it ?
             
             here you see the request