fix: get permissions for the extension for the payment domain instead of motion domain

[bassgeta]

Description

O N E L I N E R

Basically, the lookup for the voting reputation's permission proofs was done for the motion domain instead of the domain the funds are getting sent from.

Testing

1. Install the voting reputation extension
2. Create a simple payment motion sending some CREDS to leela from Andromeda, but create the motion in General (you can note how many CREDS she has)
   
3. Fully support it and run npm run forward-time 1 to get to the finalization step
   
   
4. Try finalizing it, it should pass (double check if the CREDS came to leela's wallet
   
5. For a sanity check, create a simple payment motion paying some CREDS from Serenity and create the motion in Serenity, support it, forward time, finalize it
   
   

Diffs

Changes 🏗

• use domainId instead of motionId for permission proofs lookup of the voting reputation extension

Resolves #3287

[mmioana]

Lovely what a simple fix this was @bassgeta 🎉

Created a payment motion in General with funds from Andromeda

And then one having Serenity as both the created in domain and from domain

Let's get this fix merged 🦾

[rdig]

Short and sweet, nicely done!

[Nortsova]

Great one line solution 🥳

Tested for both Andromeda created in General
Tested for both Serenity created in Serenity

Creds for Leela increase as expected: