foreman will start all services/daemons that you need for a
full fledged OBS. There is currently an issue with
thinking sphinx

https://github.com/pat/thinking-sphinx/issues/1049

That's why this is commented out. Nevertheless ts will
be started by clockwork.

Enable Rubocop Lint/InheritException

to build images without the need to hook into rpm build process

This fixes the following rubocop issue:

```
Offenses:

app/controllers/webui/package_controller.rb:685:5: W: Do not shadow
rescued Exceptions.
    rescue APIException, StandardError => e ...
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
```

Migration: Set repositories.remote_project_name NOT NULL

[ci] Enable Lint/NestedMethodDefinition Rubocop cop

Replace ERB templates with HAML for webui/notifications controller views

[webui] Add link 'more info' in package flash error

[ci] check that unpublish on project removal is working for sure

Replace ERB templates with HAML for webui/download_on_demand views

Checks for nested method definitions

Replace ERB templates with HAML for webui/search controller views

Replace ERB templates with HAML for Patchinfo controller views

Introduce Pundit authorization to Attrib-API

it must have been broken in the past (just had to remove quite some repos
on production)

[api] add index to events sent_mail

[ci] Improve apidocs controller tests

Remove methods that became less complex from blacklist

The test passed before but since the new implementation of the Attrib
policy, it responds with a 403 permission denied error (which makes
sense because the user 'adrian' doesn't have any permission to change
that attribute)

* Group setting embargo date and testing it together
* Add iand update comments to help understanding the code

The old test was not correct and the user never had the correct
permissions. So we needed to fix the old test case and tested for the
correct response code (:forbidden).

In our test environment only fred, king and Admin are allowed to
add the Issue Attribute to a project.
Because of that the test failure was correct and we had to adopt our test
suite by:
* Verifying that users that lack permissions are not allowed to add
  Attributes to a project
* Users that are permitted via role permissions are allowed to add
  an Attribute

[ci] Test source_controller

This commits brings back the old API behaviour. The old API was
validating the attribute and its values before running the permission
checks. To make this possible we have to process all attribute values
first and validate the attribute.

Before we had this logic in our controller. This code should
belong to the model and cleans up the controller.

Before we tested for the deletion of non-existant attribute. Now we're
testing if the user is allowed to delete existing attribute types.

It gives the user more information about what causes the exception.

[webui] Redirects /apidocs to /apidocs/index

It is called in teh old test suite from `project_controller_tests.rb#test_updating_config_file`.