Log allowedHosts missing value checks and skip allowedHosts on resets

[evantahler]

This PR closes #21921.

#21676 introduced a check to ensure that the interpolated values required for allowedHosts from connector configs was present, and threw an error if missing. This caused on call errors (https://github.com/airbytehq/oncall/issues/1373). #21923 removes the throw, and this PR figured out what went wrong.

Reset Connections
A Reset connection is a bit of a hack. The source the connection normally uses is replaced with a "mock" source that produces no records. This source also doesn't get the config which is normally associated with the source. This is why, for reset connections, https://github.com/airbytehq/oncall/issues/1373 occurred.

Logging

For now, we can log if there's an error interpolating the values needed for allowedHosts, rather than throwing an error.

airbyte-worker | 2023-01-26 19:42:58 ERROR i.a.w.u.ConfigReplacer(getAllowedHosts):60 - The allowedHost value, '${host}', is expecting an interpolation value from the connector's configuration, but none is present

[github-actions]

Airbyte Code Coverage

File	Coverage [39.95%]	❌
ConfigReplacer.java	92.39%	🍏
DockerProcessFactory.java	72.69%	🍏
GenerateInputActivityImpl.java	1.2%	❌
KubeProcessFactory.java	0%	❌

Total Project Coverage	23.99%	❌