update hooks lookup to use <hook>.d/* from repository hooks dir

the order would be:

1. <repository>.git/custom_hooks/<hook_name> - per project hook
2. <repository>.git/custom_hooks/<hook_name>.d/* - per project hooks
3. <repository>.git/hooks/<hook_name>.d/* - global hooks

only executable files are matched and backup files excluded (*~)
and the resulting list is sorted per each lookup

This commit adds the option of having another set of global custom hooks
along with the already supported repository local custom hooks.

The repository local custom hook is executed first (if available). If
successful, execution continues with the global custom hook (if available).
This way, local custom hooks get priority over global custom hooks.

Global custom hooks can be enabled by placing an executable file into the
"custom_hooks" directory within gitlab-shell (create if it does not exist,
yet).

This commit takes the GitlabCustomHook a bit clother to the other hook
handling classes by receiving the repo_path as argument to initialize()
instead of passing it to each method.

This commit fixes an issue where an existing but unexecutable hook would
cause an uncaught execption.

Fetch repositories with --prune option by default.

This will allow us to not recreate branches that has been deleted on the upstream and the mirror.

Related issue: https://gitlab.com/gitlab-org/gitlab-ee/issues/1277

I've reviewed the code for updating local and remote mirrors also  I've manually tested these features and all looks good.

Here is the description of the `--prune` option:


> --prune
>
> Before fetching, remove any remote-tracking references that no longer exist on the remote. Tags are not subject to pruning if they are fetched only because of the default tag auto-following or due to a --tags option. However, if tags are fetched due to an explicit refspec (either on the command line or in the remote configuration, for example if the remote was cloned with the --mirror option), then they are also subject to 


@brodock do you see any issues when fetching repos for GitLab Geo?

See merge request !110

This will allow us to not recreate branches that has been deleted on the upstream and the mirror.

Fix gitlab_custom_hook dependencies

See merge request !107

Add instrumentation to push hooks

See merge request !106

Related to #22053

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Use full repository path instead of extracting name

In order to implement nested groups https://gitlab.com/gitlab-org/gitlab-ce/issues/2772 we can not rely on old path with one slash that split namespace and project name like `namespace/project.git`. Now it can be both `namespace/project.git` and `namespace/namespace/namespace/project.git`. Because of that it makes no sense to extract part of full path. Instead we just pass path to API without change and let rails application do parsing/extraction. 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

See merge request !102

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Git LFS remark in readme is no longer correct.

See merge request !101

Re-use the default logger for performance metrics

See #64 for the discussion leading up to this.

See merge request !100

This removes the need for configuring anything extra. To make scraping
easier each line is prefixed by "metrics:".

Fixes #64

Instrument GitLab Shell and log metrics data to a file

See merge request !98

Test against ruby 2.3

Closes #61

See merge request !99

Fix rsync with ionice command building

See merge request !97

Fix short circuit logic between rsync with and without ionice for storage migrations

See merge request !96

storage migrations

Re-exposing GL_ID to custom hooks

closes https://gitlab.com/gitlab-org/gitlab-ee/issues/995
closes https://gitlab.com/gitlab-org/gitlab-shell/issues/53

See merge request !95

Update VERSION

Was this an oversight? Should we re-tag v3.6.2? Or just bump to v3.6.3?

See merge request !94

Enable GIT_TRACE_PERFORMANCE through a config variable.

The value of the variable must an absolute path needs to exist so we’re able to check if we can write in that file. Because in the 
case we cannot write we’ll throw a warning to the output of the users.

```sh
~/dev/gitlab/local/pacoguzman/gitlab-ce (master=)$ git push origin master
warning: could not open '/wadus' for tracing: Permission denied
Everything up-to-date
```

Closes #59

See merge request !91