Add approve to asset setting permissions

[rossneilson]

User Story
As a treasury management user I want to set permissions on assets so that they can be directly transferred but also approved and spent via function calls

Alternative Solutions
Similar to how we have spending calls combine 2 actions into one we need this here also. When asset permissions are set there should be two calls to the permission registry, one to set transfer signature and one for approve signature. But both should appear inside the one action on the action builder. Order is not important

Additional context
We currently only set transfer signature but need approve(spender, amount) also

[MiltonTulli]

I think the order is important since when decoding actions we assume that the approval call is previous to the call that needs to be approved. So would be good to have the same structure. [approval, transfer]

[rossneilson]

Makes sense to do it this way but it actually doesn't matter what order we set the permissions in since it is not actually calling the approval or transfer functions

[rossneilson]

Quick update on this. After thinking and discussing with Milton I think the best way to achieve this feature will be to just create two separate actions not joined together as we haven't really architected things to be able to continue adding joint actions like with spending call.
So the new user behaviour would be:

1. User sets permissions for a token the same way they did before
2. Two actions are added "Set transfer permissions for token X" and "Set approval permissions for token X"

This should be easier to implement, cleaner in the code and actually gives the user more flexibility since they can chose to remove one of the permissions