Skip failing activation-key tests

Creating an activation key with these options fails, as it should:

* max_content_hosts=-5
* max_content_hosts='ABcd37'

However, creating an activation key with these options succeed:

* unlimited_content_hosts=True, max_content_hosts=-5
* unlimited_content_hosts=True, max_content_hosts='ABcd37'
* unlimited_content_hosts=True, max_content_hosts=5

As demonstrated above, the API allows an invalid value for the
`max_content_hosts` argument when `unlimited_content_hosts` is true. When this
occurs, the `max_content_hosts` option is entirely ignored. Here's a concrete
example:

    >>> attrs = entities.ActivationKey(
    ...     max_content_hosts='ABcd37',
    ...     unlimited_content_hosts=True
    ... ).create()
    >>> for attr in ('max_content_hosts', 'unlimited_content_hosts'):
    ...     print(attrs[attr])
    ...
    None
    True

See bugzilla bug 1156555 for more information. Skip tests due to this bug:

    $ nosetests tests/foreman/api/test_activationkey.py  -m test_negative_create_3
    SSS
    ----------------------------------------------------------------------
    Ran 3 tests in 0.518s

    OK (SKIP=3)
Merge pull request #1619 from Ichimonji10/activation-key

Skip failing activation-key tests
Drop booby, let nil values be submitted to API

Drop dependency on booby.

* Make class `Entity` inherit directly from `object`. Define method
  `Entity.__init__`, and make that method handle whatever instantiation logic
  booby formerly did. (but better!)
* Make class `Field` inherit directly from `object`. Define method
  `Field.__init__`, and make that method capable of recording the instance
  attributes `required`, `choices`, `default` and `null`.

This has several positive effects. First, fewer methods are necessary.

* Drop method `robottelo.factory.field_is_required`. The `required` attribute is
  guaranteed to exist on all `Field` classes, so it is possible to just call
  `SomeField.required` instead.
* Drop method `robottelo.orm.Entity.get_values`. It is now possible to just call
  `vars(SomeEntity)` instead.

Second, all classes inheriting from `Entity` and `Field` have a more
comprehensible inheritance tree and sane instantiation process. An `update`
method is no longer inherited from booby, which means that an
`EntityUpdateMixin` may finally be created without MRO issues, and no metaclass
magic is used. Incidentally, a pylint error stating that many `Entity`
subclasses have too many ancestors is now gone.

Third, it is now possible to pass `None` values into classes. This fixes #1082.
Formerly, this behaviour was exhibited:

    >>> from robottelo.entities import Organization
    >>> for org in (
    ...         Organization(name='ACME'),
    ...         Organization(name='ACME', description=None),
    ...         Organization(name='ACME', description='Better than ACNE!')
    ... ):
    ...     org.get_values()
    ...
    {'name': 'ACME'}
    {'name': 'ACME'}
    {'description': 'Better than ACNE!', 'name': 'ACME'}

This is the new behaviour:

    >>> from robottelo.entities import Organization
    >>> for org in (
    ...         Organization(name='ACME'),
    ...         Organization(name='ACME', description=None),
    ...         Organization(name='ACME', description='Better than ACNE!')
    ... ):
    ...     vars(org)
    ...
    {'name': 'ACME'}
    {'description': None, 'name': 'ACME'}
    {'description': 'Better than ACNE!', 'name': 'ACME'}

Drop a `pylint:disable` directive from module `robottelo.entities`. All classes
inheriting from `Entity` now have an `__init__` method.

These changes do not appear to break anything. Module `test_multiple_paths` is
in good shape:

    $ python -m unittest tests.foreman.api.test_multiple_paths
    …
    ----------------------------------------------------------------------
    Ran 238 tests in 154.352s

    FAILED (failures=1, skipped=62)

The one failed test relates to activation keys, which is a known issue. `make
test-robottelo` also succeeds.