Making the `gettext:updated_check` by completely regenerating the gitlab.pot.

This avoids an issue where `gettext:find` would not pick up on changes
if the file isn't removed first.

If you called rake gitlab:db:drop_tables before running gitlab-ctl
reconfigure (or rake gitlab:db:configure)

Since we are only using `.po` files for translation we can shave off
some setup time.

Generating the `mo` files also regenerates the PO-files, including
fuzzy translations. Those cause a lot of bugs, and we don't need them
anymore since the `po` files are generated by an external translation service.

This makes the output in static analysis a bit more verbose.

The cache state for Wikis that were imported via GitHub or Bitbucket does
not appear to have been flushed after a successful import.

Closes #47546

Signed-off-by: NRémy Coutable <remy@rymai.me>

Closes #46530.

Closes #43706.

Direct disk access is done through Gitaly now, so the legacy path was
deprecated. This path was used in Gitlab::Shell however. This required
the refactoring in this commit.

Added is the removal of direct path access on the project model, as that
lookup wasn't needed anymore is most cases.

Closes https://gitlab.com/gitlab-org/gitaly/issues/1111

Before this change, trying to setup dev environment could be tried
without having at least one Gitaly running. Cloning the repositories
would fail, but not stop the setup.

Given this would lead to an inconsistent state, a check was added if we
could connect to the server.

Output when it fails:

```
$ rake dev:setup
Failed to connect to Gitaly...
Error: 14:Connect Failed
```

* Use the correct key prefix
* Clear old cache keys

TODO:

At some point we could remove clearing old cache keys.

* ask_to_continue
* Gitlab::TaskAbortedByUserError

Signed-off-by: NTakuya Noguchi <takninnovationresearch@gmail.com>