bug: multi-signature-registration cannot have a custom fee

[ciband]

Expected Behavior
The multi-signature-registration constructor takes in a optional fee. This fee should be used in the transaction, or a custom fee should not be available.

Current Behavior
If you specify a custom fee, this fee is overridden when you set the public keys or add a participant.

Possible Solution
Either the custom fee should be removed from the constructor if it should not be customizable, or the fee should be used in the class.

Steps to Reproduce (for bugs)
Write a unit test, using a custom fee. Assert the custom fee value. The test will fail.

Your Environment
Python 3.9, Windows

• Version used: master branch, tips

[ciband]

I don't mind fixing this one but I am not sure what the expected behavior is. Please advise.

Thanks.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.