Now that we have dropped V0 encoding logic, we can safely add the predicateData to the predicate resources and inputs since there is no need to handle the bytes padding within predicate arguments to handle the dynamic size of the array of policies.

We still need to have the populateTransactionPredicateData in place because there are some scenarios where predicate-fetched resources will not include the predicate and predicateData.

I believe this mostly happens within wallet connectors, where the connector Account is instantiated using the predicate address, and the predicate is instantiated only before submitting the TX.