Remove direct syslog logging from capi

[Benjamintf1]

Capi logs it's stdout output and stderr output generally to two places:

1. a location within /var/vcap/sys/log for local storage
2. to rsyslog for use to export to an external location

At some point syslog-release introduced the ability to tail logs within /var/vcap/sys/log directory (the subproject was pulled from concourse). This would give the platform owner to forward all os level logs from every vm, as well as every cf system log to an external database for storage and debugging (i think there's s3 use cases, splunk, so on).

However because capi had a forwarding feature to syslog before the file tailing feature, it sends logs externally twice. (syslog-release has some special functionality to reduce some of the impact https://github.com/cloudfoundry/syslog-release/blob/4fd5d0d070a283912700006187be5bf66aa9000b/jobs/syslog_forwarder/templates/syslog-release-file-exclusion.conf.erb#L1-L2 https://github.com/cloudfoundry/syslog-release/blob/4fd5d0d070a283912700006187be5bf66aa9000b/jobs/syslog_forwarder/spec#L82-L93).

What i propose we do with capi is remove direct forwarding of logs to rsyslog from capi and rely solely on file forwarding, removing the duplication.

[wayneeseguin]

Sounds like a good plan to me.

[philippthun]

No concerns from our side as well.