RSDK-5140 Don't override a local config BindAddress with a default one from Cloud

[aldenh-viam]

In reader.go:fromReader: the initial read of both local and cloud configs.

In entrypoint.go:configWatcher: runs on detected config file changes.

Bind Address order of precedence is now:

1. Non-default coming from Cloud
2. Non-default from Local
3. Default from Cloud/Local

Possible alternative:
Update all Cloud read functions with a parameter to include/exclude returning the default BindAddress. Note that the default BindAddress is not really coming from Cloud, but rather patched with a constant defined in rdk.

[cheukt]

I'd like to see a log of some kind for each of these cases:

• Non-default coming from Cloud that overrides non-default from local - something like "cloud config specifies port XXX, overriding port from local config XXX. starting server on port XXX"
• Non-default coming from Cloud that overrides default from local - something similar to the above log
• non-default from local overriding default from cloud - something like "local config specifies port XXX, overriding default port from cloud XXX. starting server on port XXX"
• default port from cloud - "starting server on default port from cloud network config XXX"

basically we should be able to tell that ports were defined and explicitly overridden through the logs

[aldenh-viam]

I'd like to see a log of some kind for each of these cases:

* Non-default coming from Cloud that overrides non-default from local - something like "cloud config specifies port XXX, overriding port from local config XXX. starting server on port XXX"

* Non-default coming from Cloud that overrides default from local - something similar to the above log

* non-default from local overriding default from cloud - something like "local config specifies port XXX, overriding default port from cloud XXX. starting server on port XXX"

* default port from cloud - "starting server on default port from cloud network config XXX"

basically we should be able to tell that ports were defined and explicitly overridden through the logs

Isn't the current behavior already everything except the third (non-default local overrides default from cloud)? I'll add that one, but is it necessary to log all the others? I think users shouldn't really be expecting to be able to override cloud options with their local config unless we want to explicitly add that feature. Alternatively, I can always log the BindAddress and the source it retrieved it from. EDIT: discussed offline, we'll log 1 and 3, as they seem to be the two cases that have confused users in the past.

[cheukt]

LGTM

[cheukt]

prefer using logger.CInfof, even if it wouldn't matter in this case