Attempt to debug the /new/package UI endpoint wrt the error messages
Remove debugging code and FIXME statement since the tests now passes on jenkins
Specify clearly that the critpath argument is optional

This is mandatory otherwise we cannot have critpath=False, it will always
be True.
Attempt to fix the differences b/w a local test run and jenkins
Remove debugging and FIXME statement as the tests are now passing in jenkins

Fixes https://github.com/fedora-infra/pkgdb2/issues/8
Create the AdminAction class and its search function
Add the add_new_request_branch method to the internal API

This method allows register a new branch request in the AdminActions
table.
Update the logs to support package.branch.request send upon new branch request
Expose the search_actions method in the internal APi

This method behaves similarly to the search_logs method by allowing the
user to find the actions requiring admin intervention matching a set of
criterias
Add a dedicated form to request a new branch for a package
Add the admin_actions endpoint

This endpoint exposes the actions requiring admin intervention in a
similar manner as the admin_logs endpoint
In the front page of the admin section add the link to admin_actions
Add the list_actions template required for the admin_actions endpoint
Add the request_branch template used to request a new branch for a package
Add the package_request_branch endpoint allowing to request for a new branch on a package
Forward to the package's detail page if there are branches that are 'missing'

These branches could thus be requested (allows us to display or not the
`request new branch` button)
Add the `Request new branch` button if it makes sense and make it a pop-up as the others
Link the user and the package to their respective pages
Make the action table a little prettier
Give a little space on both sides of the cells