Bug: Changing VAN API key in UI does not commit to DB

[RahulR100]

Describe the bug
Changing VAN API key in UI does not commit to DB

To Reproduce
Steps to reproduce the behavior:

1. Change VAN API key in UI
2. Go to organization DB
3. See old key in place
4. Encrypted key DOES change however

Expected behavior
VAN API key should be updated

Additional context
Everything should use the encrypted key anyways?

[jb-cloud]

I have personally confirmed this behavior.

When overwriting or blanking out an existing key in the UI, only the new encrypted key and app name are written to organization > features. The plain text api NGP_VAN_API_KEY key value is not updated.

This breaks, at least, calling VAN's survey question endpoint needed to populate the list of available questions when mapping interactions to VAN survey question responses when using the the ngpvan action handler. In the UI, the user simply sees a "0" under action handler.