The kardex_tray field indicates it is a tray, but we still needed
to identify a whole kardex shelf. On the 'stock.kardex' model, we
must select the corresponding location.

Add a tray_matrix widget on stock location form view for convenience:
easy to see which cells contain stock or not.

* Display "No operations" when we have cleared the queue
* Hide the information fields when there is no operation to do
*

Setup a hierarchy:

 * A View
   * contains Shuttles
     * contains Trays
       * contains Cells

A default view is created for all the Kardex.

* Prevent disabling locations or tray types in use
* Prevent changing tray type if any cell contain stock
* Add a button to show the locations using a tray type from the tray
  type form
* Prevent changing a tray type size when used
* Remove tray name in cell name: redundant in the display name
* Add filters on location search view to search by tray type and kind of
  kardex "object" (view, shuttle, tray, cell)
* Remove an unused action

* Add missing dependency
* using the direct path to the Serialized class will work in every
scenario (eg. pytest) without having to add base_sparse_field in --load

Allow to specify an action, example on the location view: open the location
with the clicked coordinates.

Preparing the module to be a generic core for supporting Vertical Lifts
/ Carousels. The Kardex one willbe a submodule.

The default one being 'simulation', new ones must be added by other
addons. An empty shell is created for Kardex, where we'll later add the
"driver" part to drive Kardex Shuttles.

Following the proposal of @damendieta, implement differently

It has been extracted in another addon
(OCA#719)

* Add vertical_lift_shuttle_id field on stock.location, help to find the
shuttle for a location
* Add StockLocation.fetch_vertical_lift_tray(), that needs to be
implemented in addons to send commands to the hardward to fetch a tray,
and if existing show a cell (laser pointer, ...)
* Add helpers on stock.move.line fetch_vertical_lift_tray_source() and
fetch_vertical_lift_tray_dest() that fetch the tray directly from a move
line's source or destination location

The way to connect to a vertical lift can change from a model to
another.
Let's not suppose every system needs an address per shuttle.
For instance, kardex may have a single server for all the shuttles.
That needs to be handled in the kardex specialized module.

Namely, the pick/put/inventory operations are now split in
different models.

Pick and Put share a model and customize their behavior, which is pretty
similar. The inventory operation will have a different view and
different workflow.

This changes will ease a lot the customization of the different
workflows and views.

When we refresh the page on the browser when we are using the "screen"
view, odoo loses the information that we want the view to be headless,
fullscreen, etc. so it's displayed pretty badly.  This view is a
work-around: its priority is lower, so it will be picked up by default
on loading, and a button allows to re-open the screen view with the
proper options.

There is no such action as 'ir.actions.do_nothing', it kinda works,
until you look into the js console and stares at the errors.

There is a nice OCA module that serves this purpose (more or less,
because it reloads the window, this is not an issue).

Example of usage in an odoo shell, when a screen is open:

>>> self.env['vertical.lift.shuttle'].browse(1)._operation_for_mode().operation_descr = 'foo'
>>> self.env['vertical.lift.shuttle'].browse(1)._send_notification_refresh()
>>> env.cr.commit()

Provided the longpolling is correctly configured with a proxy, the
screen should immediately refresh with 'foo' as operation description.