Fix epics from sub-groups errors on reorder, delete

See merge request gitlab-org/gitlab-ee!11837

Give reviewer roulette its own header in the docs

See merge request gitlab-org/gitlab-ce!27883

Clarify that reporters can manage boards

Closes #60794

See merge request gitlab-org/gitlab-ce!27616

Docs aren't reviewed using roulette

Closes #61047

See merge request gitlab-org/gitlab-ce!27876

Resolve "ArgumentError: Trait not registered: timeouted"

Closes #11392

See merge request gitlab-org/gitlab-ee!11948

Reviewer roulette via Danger should take OOO status into account

Closes #57652

See merge request gitlab-org/gitlab-ce!27696

Also regenerate gitlab.pot

Fix letter opener gem error: "undefined method `before_filter' for LetterOpenerWeb::LettersController:Class"

See merge request gitlab-org/gitlab-ce!27769

Extract refactoring from !10755

See merge request gitlab-org/gitlab-ee!11515

Refactor LfsImportService and ImportService

See merge request gitlab-org/gitlab-ce!27255

In order to make `LfsImportService` more reusable, we
need to extract the logic inside `ImportService` and
encapsulate it into the service.

Disable method replacement in avatar loading

Closes #60903

See merge request gitlab-org/gitlab-ce!27866

Uninstall cluster applications (backend services)

Closes #60665

See merge request gitlab-org/gitlab-ce!27096

These builder methods are using user provided input inside a public_send
but this is safe to do in this instance because before they are called
we check before calling them that they match an expected application
name.

In order to not miss any errors since we are not checking the return
value of update

Basically does the reverse of after_transition to :installed.

Add endpoint to delete/uninstall a cluster application

Add specs

Only prometheus can be uninstalled atm, the rest will be dealt with
later.

Presumption is that new application types will have uninstallation
implmemented at the same time.

Rescue and put into :uninstall_errored if something goes wrong while
destroying, which can happen. I think it is safe to expose the full
error message from the destroy error.

Remove the :uninstalled state as no longer used.

+ to monitor progress of uninstallation pod