Remove owner on consul_service to avoid order of operation error

With Consul Service Discovery, in certain cases a given recipe will try to add a consul_service before the Consul recipe has run. This can result in an error because the gitlab-consul system user doesn't yet exist.

consul_service[rails] (gitlab::unicorn line 31) had an error: 
Chef::Exceptions::UserIDNotFound: file[/var/opt/gitlab/consul/config.d/rails-service.json] 
(/opt/gitlab/embedded/cookbooks/cache/cookbooks/consul/resources/consul_service.rb line 38) had an error: 
Chef::Exceptions::UserIDNotFound: cannot determine user id for 'gitlab-consul', does the user exist on this system?

In this case, the Unicorn recipe ran first. As it happens, it's not really important that the file be owned by gitlab-consul so let's just remove it to avoid the problem.

This is a followup to !3295 (merged)

Fixes: #4432 (closed)