Run migrations if gitlab is upgraded by `gitlab install`

At the moment only the `setup gitlab database` exec is run on
first run or until the `.gitlab_setup_done` file is deleted. But
upgrading gitlab normally requires running the db migrations.

This PR also adds some additional tasks to the `precompile assets`
exec that cleans the assets before precompiling as well as cleaning
the cache.

- Fixed spec test cases
- Fixed lint warnings
Merge pull request #125 from tPl0ch/feature-db-migrations

Run migrations if gitlab is upgraded by `gitlab install` (Closes: #120)
Add param to set bundler flags
Merge pull request #127 from atomaka/atomaka/feature/bundler-flags

Add param to set bundler flags
[specs] Clean params_set (closes: #128, refs: #126)
prepare release 0.1.3
Merge pull request #128 from sbadia/feature/128/clean-specs-params

[specs] Clean params_set
[spec] fix puppet-rspec regexp (refs: #126)

According Andrew comment on
https://github.com/sbadia/puppet-gitlab/pull/126#issuecomment-37826055
our regexp can match not wanted things… this commit fix this problem.

Thanks Andrew!
Merge pull request #129 from sbadia/feature/126/better-matchs

[spec] fix puppet-rspec regexp (refs: #126)
[spec] Add class coverage with rspec-puppet 1.0.6
[spec] Add syntax checks and use new coverage tasks
[spec] Add git package coverage yay! 92%
[spec] Add init coverage yay! 100%
[spec] Update with new raise_error syntax
Merge pull request #131 from sbadia/feature/coverage100

[specs] To infinity and 100% code coverage !!!
Add param for Google Analytics
Merge pull request #130 from atomaka/atomaka/feature/google-analytics

Add param for Google Analytics
Add git_proxy parmeter
[readme] Add missing options / documenation
[templates] Remove lg GIT config alias