1. When we have a stack of switches, the same IP is associated to several
   switches
2. Move the items <-> host assocation to the item create/edit page

JIRA INFRA-267

JIRA INFRA-281

"type" field on host replaced with foreign key "machine_type_id"

JIRA INFRA-281

Allow to filter by domains

- add domain_id on NetworkScope table to define a default domain
- add domain_id on Network (default to the Network Scope one)

Fixes INFRA-194

The string representation of a Network is the vlan_name.
This is what we should allow to pass as string to create an interface.

Note that if we pass network_id instead of network when creating
and interface, the validate_interfaces method from the Network class
is not called.

All endpoints are plural

Pagination information (next, prev, first, last) is included in the Link
HTTP header.
The total number of entries is provided in the X-Total-Count HTTP
header.

text is really generic and could conflict with another variable.
body is often used for comments.

Required to create users when importing items from JIRA.

Renamed blueprint from "users" to "user" to be consistent with other
blueprints (inventory and network).

+ fix tests

This allows to easily register items via the API without giving an ICS
id.

Split API in different blueprints like for the web UI:
- users (login)
- inventory
- network

Use version in API url (api/v1) to make future changes easier without
breaking backward compatibility

- Rename Host to Interface
- Create new Host table to group interfaces

- All created tokens are stored in the database.
  To revoke a token, we just delete it from the database.
  Tokens not found in the database are thus considered unvalid / revoked.

- Add button to copy generated token to the clipboard

- Redesign profile page

- Several IPs (hosts) can be associated to one MAC address
- Host name shall be non nullable

- refactor Network class

- network name should be unique and not nullable
- force all name fields to StringField

Use full exception error as message (error messages from psycopg2 can
be quite long but that makes it much more explicit)

TODO: we should maybe raise ValidationError in models
and catch that to raise CSEntryError in the API

- Allow to pass several mandatory fields in create_generic_model
- Add tests

- catch IntegrityError on patch
- disable autoflush (IntegrityError was raised before commit due to
autoflush)

Pass ?qrcode=true as query string

Can use:

  -  /api/items?serial_number=123456
  -  /api/items?location_id=1

- add more tests
- patching an item update children location and status
- setting the parent on an item updates the location and status with the
  parent ones

Most items won't have a name.
hostname could be added in a separate table if required.