[FIX] mrp: force empty domain to reset action at upgrade

There was a domain in 7.0 but it must be forced
to empty during upgrade, as the MRP BoM model
has changed.
[FIX] openerp/osv/fields: disable prefetching when reading inverse of one2many fields

This fixes issue #2146.  The inverse of a one2many field can be an inherited
field (_inherits).  In that case, we cannot read its value with a simple
database query.  Instead, we let the related field read it, but for performance
considerations we disable the prefetching of other fields.
[FIX] website.editor: need to set the range on start because the browser can be lost the caret and can't insert the media in the page.
[FIX] website_event_sale: need to use new api to send the context. Add some step for test to check if the cart have the distinct products
[FIX] website_sale: Price of accessory product are all time null. Need to use new api to send the context.
[IMP] Add possibity to add rereserve button and optimize action assign
Merge pull request #2312 from odoo-dev/8.0-wmsoptimassignrereserve-jco

[IMP] Add possibity to add rereserve button and optimize action assign
[ADD] l10n_do: Chart of Account for Dominican Republic

Fixes #2257
[FIX] web: FieldBinaryImage upload file at the right place

Before this, the div wasn't in the right place in the form view
for instance, in the product form view, the third checkbox triggered this binary upload file
opw-613318
task-8982
[FIX] web: revert 9f0834771d49a

Revert "[FIX] web: base.css: fixed width for input of file type under oe_avatar"
A better fix for opw-613318 is done in f8bd25c852e
[FIX] point_of_sale: prevent the company logo from being cached by the browser by accessing it via a random URL
[FIX] models: in method onchange(), check for record dirtiness only on *2many fiels

Cascading onchanges can be caused by a related field computed in cache.  This
causes a bug in sale order lines, were setting the uom field forces reading
product fields, which are inherited from product templates.  The inherited
fields are computed as related fields, which marks the product record as dirty.
This subsequently triggers an onchange on the product field, which resets the
uom field!
[FIX] point_of_sale: chrome was dropping the cookie when loading the company logo, resulting in an incorrect logo in multi-db setups.
[FIX] mrp: force empty values for fields that were dropped

This ensures the field values are cleared during
upgrades from previous versions
[FIX] product,purchase,point_of_sale: force empty values for dropped fields

At 96f038a product-related fields were removed due
to an important product.template/product.product
refactoring. As the field values were simply
dropped, they may not be nullified when upgrading an
existing database. Forcing them to False will take
care of it.
[FIX] hr_recruitment: fixed computation and storage of day_open and day_close + assignment of date_open and date_closed.
[FIX] sale: force default values for dropped fields

Those values were dropped at rev 3b636a5 but
need to be forced back to default so older
databases get properly updated when upgrading.
[FIX] mrp: force default values for dropped fields

Those values were dropped at rev 9b34358 but
need to be forced to empty so older databases
get fixed when upgrading
[FIX] website_event_track: force type from related to fix bug with convert_to_cache on picture
[FIX] website_blog: wait that document is ready before to check if we need to update menu for blog