to be able to debug server side service failures

Fix issue 1723 and add some tests

[api][webui] Fix rake tasks from outside the apps directory

If you require files in the Rakefile then from where the Rakefile
lives please.

Gems

we use version 10.4.2 as provided by ruby 2.3.1

[vagrant] fix startup bugs

Remove file test

Pkg controller test requests 5

This makes it easier to parse migrated tests.

https://github.com/openSUSE/open-build-service/pull/2059#discussion_r75876782

Kudos to Karsten Keil for the fix.

* Use rails tag helper for hidden fields and checkboxes
* Simplify setting global role and user state in view

Update OBS to Rails5

[webui][ci] Update admin handling in user model

======

Failures:

  1) Packages editing package files editing an existing file
     Failure/Error: page.execute_script("$('.CodeMirror')[0].CodeMirror.setValue('added some new text')")

     Capybara::Poltergeist::JavascriptError:
       One or more errors were raised in the Javascript code on the page. If you don't care about these errors, you can ignore them by setting js_errors: false in your Poltergeist configuration (see documentation for details).

       TypeError: 'undefined' is not an object (evaluating '$('.CodeMirror')[0].CodeMirror')
       TypeError: 'undefined' is not an object (evaluating '$('.CodeMirror')[0].CodeMirror')
           at phantomjs://webpage.evaluate():1
           at phantomjs://webpage.evaluate():1
           at phantomjs://webpage.evaluate():1
           at phantomjs://webpage.evaluate():1
     # ./spec/features/webui/packages_spec.rb:58:in `block (3 levels) in <top (required)>'
     # ./spec/support/logging.rb:4:in `block (2 levels) in <top (required)>'

Empty params get skipped currently. Might be related to https://github.com/rails/rails/issues/23438

This commit workarounds the problem.

[ci] Skip test to avoid random test failure in our ci which is running inside our rpm package build....

This will set the default entries on the user page to 10. Valid values are 10, 25, 50 and 100.

Some tests started to fail due to encoding errors when doing http POSTs.
Since those tests were sending the data in the request body, not the parameter,
we could simply switch back to using raw_post. As we did before.

Partly reverts 6ad6ed6f

because Rails raises now an ActionController::BadRequest error, so raising an ApiException is not necessary anymore.
See Rails commit 59ab2d1ee5995d9ea27ca60e92576518c1898c59.

Minitest::Assertion:
    --- expected
    +++ actual
    @@ -1 +1 @@
    -[{"name"=>"images", "arch"=>["x86_64", "i586"]}, {"name"=>"Base_repo", "path"=>{"project"=>"BaseDistro2.0", "repository"=>"BaseDistro2_repo"}, "arch"=>["x86_64", "i586"]}, {"name"=>"10.2", "path"=>{"project"=>"BaseDistro", "repository"=>"BaseDistro_repo"}, "arch"=>["i586", "x86_64"]}]
    +[X({"name"=>"images", "arch"=>["x86_64", "i586"]}), X({"name"=>"Base_repo", "path"=>X({"project"=>"BaseDistro2.0", "repository"=>"BaseDistro2_repo"}), "arch"=>["i586", "x86_64"]}), X({"name"=>"10.2", "path"=>X({"project"=>"BaseDistro", "repository"=>"BaseDistro_repo"}), "arch"=>["i586", "x86_64"]})]
    test/functional/webui/add_repo_test.rb:27:in `test_add_default'

Follow up of changes made in rails 5 regarding parameter handling.

Also fixes:

test_trigger_rebuild_via_binaries_view                         ERROR (56.67s)
Capybara::ElementNotFound:         Capybara::ElementNotFound: Unable to find css "#flash-messages"
            test/functional/webui/package_controller_test.rb:544:in `test_trigger_rebuild_via_binaries_view'
            test/test_helper.rb:124:in `block in __run'
            test/test_helper.rb:124:in `map'
            test/test_helper.rb:124:in `__run'

When a browser, or capybara, provided the (boolean) value of show_all parameter as
a string, the setting were always interpreted as true. This caused one of our tests
to fail and was also reproducable in firefox (44.0.2).

=======

3) Webui::ProjectController GET #index showing not home projects should eq 1

     Failure/Error: it { expect(assigns(:projects).length).to eq(1) }
       expected: 1
            got: 2

       (compared using ==)

     # ./spec/controllers/webui/project_controller_spec.rb:53:in `block (4 levels) in <top (required)>'
     # ./spec/support/logging.rb:4:in `block (2 levels) in <top (required)>'

The element we select in our test, and we later on check for a changed label,
is invisible until the user hovers over it. To do so in our tests we have to
find() and then hover() the element.

With the recent capybara update we need to explicitly set the visible: false
parameter when calling find().

This commit upgrades dataTable from v1.9.4 (legacy) to v3.4, which is required
for upgrading to rails 5.

Paging type had to be set explicitly now (to simple) to have the previous / next format.

Icons (and css) are missing right now
  https://datatables.net/reference/option/pagingType

Converted parameter names are documented here:
  https://datatables.net/upgrade/1.10-convert
  https://datatables.net/manual/server-side

Replace deprecated assert_tag with assert_xml_tag

========

spec/controllers/webui/user_controller_spec.rb:101:43: E: unexpected token tCOLON
(Using Ruby 2.0 parser; configure using TargetRubyVersion parameter, under AllCops)
      expect(response.body).to eq({"sEcho": 2, "iTotalRecords": 1, "iTotalDisplayRecords": 1, "aaData": []}.to_json)