Addition of depositCaching parameter for gateways

[iamredbar]

General

This PR adds functionality to choose whether or not a gateway allows for cached deposit addresses/memos. While being a small change (4 lines), this adds major modular improvement by allowing for gateways with unique deposit requirements. Changes have been added to each active gateway setting this parameter equal to 'true' to continue working with prior UI functionality.

Code Preparation

• Check for unused code
• No unrelated changes are included
• None of the changed files are reformatting only
• Code is self explanatory or documented
• All written text is properly translated (english language)

Testing

The branch has been tested on the following browsers (desktop and mobile view)

• Chrome
• Opera
• Firefox
• Safari

[sschiessl-bcp]

Please code it in a way that the default value of the flag is inline with existing behavior.

[iamredbar]

Would you be able to clarify what you mean?
The default values are changed in this PR.
Do you mean if it doesn't have the flag to default to a specific value?

[sschiessl-bcp]

You are introducing depositCaching as a new value in the gateway configuration. If this flag is not present or not set, the code should behave exactly how it did before, i.e. the default behavior of other gateways is not affected if the flag is not present.

[iamredbar]

Thank you for the clarification. I will refactor.

[iamredbar]

I have updated to comply with non-use of depositCaching property. It uses a ternary operator with the object prototype method .hasOwnProperty.