TT#157800 Add CAP_CHOWN capabilities to recording-daemon

Otherwise new recordings won't have expected owner/group,
when running rtpengine as its own user

Change-Id: I8a6cf123a5467a412c1b2c3ea6c8db7fddc9dc2d
(cherry picked from commit 91169cc152)

debian/ngcp-rtpengine-recording-daemon.service

@@ -11,7 +11,7 @@ Type=notify
 LimitNOFILE=100000
 RuntimeDirectory=rtpengine-recording
 PIDFile=/run/rtpengine-recording/ngcp-rtpengine-recording-daemon.pid
-AmbientCapabilities=CAP_NET_ADMIN
+AmbientCapabilities=CAP_NET_ADMIN CAP_CHOWN
 User=rtpengine
 Group=rtpengine
 ExecStart=/usr/sbin/rtpengine-recording -f -E --no-log-timestamps --pidfile /run/rtpengine-recording/ngcp-rtpengine-recording-daemon.pid --config-file /etc/rtpengine/rtpengine-recording.conf

el/rtpengine-recording.service

@@ -10,7 +10,7 @@ Environment=CFG_FILE=/etc/rtpengine/rtpengine-recording.conf
 EnvironmentFile=/etc/sysconfig/rtpengine-recording
 User=ngcp-rtpengine
 Group=ngcp-rtpengine
-AmbientCapabilities=CAP_NET_ADMIN
+AmbientCapabilities=CAP_NET_ADMIN CAP_CHOWN
 RuntimeDirectory=rtpengine-recording
 PIDFile=/run/rtpengine-recording/rtpengine-recording.pid
 ExecStart=/usr/sbin/rtpengine-recording --config-file=${CFG_FILE} --pidfile=${PID_FILE}