Allow multiple encrypted values in Input configurations

[kingzacko1]

Description

Remove return from for loop when iterating over input configuration values so that multiple EncryptedValue fields can be supported

Motivation and Context

The short-circuiting of this for-loop only allowed for one value in an input configuration to be an encrypted value. Any others would not be transformed and the input would fail to be saved to the DB.

How Has This Been Tested?

Local dev env

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (non-breaking change)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.

[kingzacko1]

@thll this was preventing some development on a new input with multiple encrypted values going into the DB. Seems like this should be the fix, but just wanted to check with you that there wasn't a good reason for the return statement there.

[thll]

I agree that the return statement looks out of place. Thanks for fixing!