Add regions module to integration tests

Regions module should contains basic functionality that should be
shared among multiple page objects: common tables, forms,
notifications etc.. Basically every piece of code that can be reused by
multiple classes in a form of a new object should be placed in here.

* I would suggest that already created regions should be moved into this
  module.

* I would consider region everything that can be reused by at least
  two page objects and aim for maximal code reusability in the future.

* Every new region should inherit from class BaseRegion located in
  baseregion.py.

Partially implements blueprint: selenium-integration-testing

Change-Id: Ib8c20d8833e0830c85030633091663d33de6e3ab
Temporarily disable the Jasmine unit tests

A recent Jasmine package upgrade to move to Jasmine 2.x is breaking the
Horizon gate. There is other work underway to make Horizon more
compatible with Jasmine 2.x (see comment #2 in the bug for more
details), let's disable the tests for now and reenable them shortly as
part of that other work when we can make sure the upgrade to 2.x
happens when the test codebase is ready to handle it.

Change-Id: I745e8957128772a7415a20393940068dbd89a493
Closes-Bug: #1396954
Merge "Add regions module to integration tests"
Merge branch 'master' of https://github.com/openstack/horizon