Feature: consider a way to indicate what fields are sensitive

[raulb]

Feature description

The platform team has submitted this feature request. It was initially created as part of another issue: #1558.

Clients require the ability to determine which situations require obfuscating their values. My recommendation is to derive this from the data type rather than manually indicating whether the information is sensitive. This issue should track progress on this approach.

[raulb]

@jmar910 @justmisosoup fyi, created this as a separate issue rather than make it part of #1558 .

[lyuboxa]

Discussed this issue with @justmisosoup and @jmar910. We can punt on this for now until we get some more experience.
The TL;DR being warning the user from entering sensitive data as plain text vs using secrets. The intermediary plan is to handle this in the UI and guesstimate which field may be sensitive based on naming.

If the Conduit team has a suggestion on how this can be implemented besides adding sensitive field to the config fields, let us know.