[FIX] Add context propagation for m2m list view

Fix bug https://bugs.launchpad.net/openerp-web/+bug/1279885 :
    Many2many fields in Tree views will not get translated.
    If you check the context for a name_get of a m2m field, it is passed as
    None.

Add context propagation to m2m fields in list views.
Fix translation issues when viewing a a many2many field in a Tree view.
Fix sale_id on stock.picking.out view

View inheritance is on the wrong model after model change of stock.picking.
Here we just fix the model.
Overwrite translation on module update if option is set

Launchpad bug: https://bugs.launchpad.net/ocb-server/+bug/1319285
[FIX] orm: allow unicode in inherit views with attribute

When extending a view with position='attributes', prevent crash if view contains unicode char
Fixes #706
[IMP] module: when uninstalling a module, do not redirect to a useless screen
Merge pull request #17 from savoirfairelinux/7.0-m2m-context

[FIX] view_list: Add context propagation for m2m list view

If the _rec_name field of a model is translatable, the value was not translated when displayed in a list view through a many2many field (e.g. server_action_ids on base.action.rule).
[FIX] Partner VAT Intra XML delaration: Vat number format correction

The Partner VAT Intra XML delaration needs to have the VAT number
in the format without the country code prefix.

The current behaviour was to include the country code prefix in the
report which causes an SQLException error on uploading the XML file
to the Federal goverment's website.  While the error is non-descriptive
fixing the VAT number format fixes the error.
Merge pull request #739 from apertoso/7.0-bug-vat_intra

[FIX] l10n_be: VAT number for Intra XML declaration should not contain county code
[FIX] purchase_requisition: broken procurement wkf

If a purchase requisition is created instead of a purchase order for a procurement order, the method make_po should not return the id of this requisition, as methods calling the make_po method expects ids of purchase orders, not purchase requisition ids.

Besides, on purchase requisition done or cancel, we set the procurement order accordingly, without the use of the workflow. We consider this as crappy, the proper fix should be the use of a dedicated workflow for purchase requisition, but I cannot be done in stable branches. This aims trunk/master.
Merge pull request #650 from yvaucher/patch-1

[7.0] sale_stock: field sale_id should be on stock.picking.out view
[FIX] web: format.js, toString while parsing date

When attempting to parse client date, value is not always a string.
We force the toString when adding the leading 0, as the replace method is for string
Server Translation: Fixed the issue search on translated field do not return true result, search on tranlsated field fails due to expression parsing which fetches ids from ir_translation as well as working table and UNION of this makes search fruitless, also search fails for in language other then english when you enter part of a string for the field to search.
Merge pull request #622 from odoo-dev/7.0-opw-592890-msh

[FIX] search on translated field: Only search on source field if not translated.
[IMP]: Improve copy method to set stage_id in draft stage
Merge pull request #725 from odoo-dev/7.0-bug-1235237-ypa

[FIX] crm_claim: copy: reset stage + add a copy marker to the name
[FIX] fields property: do not create empty properties

fixes #595
In the case where a property for the company exists but has no related record (e.g. in case of type m2o with no defined value), not setting a value to this field for a new record would create a new property (as browse_null is not an instance of browse_record)
[FIX] purchase_requisition: duplicated stock moves

When a purchase requisition is created from a procurement order, a first stock move is created, not associated to any purchase orders
Then, on purchase order creation and confirmation, in the purchase requisition, new stock moves are created, associated to the purchase order.
The existing stock move issued from the procurement order which created the purchase requisition remained untouched, leading to wrong inventory values
To fix this, the destination location of the stock move of the procurement order is written on the source location
A proper fix should be to use a dedicated workflow for puchase requisition, but this can't be done in 7.0, it has to be done in master/trunk
[FIX] account: add multicompany rule to account.subscription.line

The wizard to generate recurring entries did not respect multicompany rules as the request was done in plain sql.
Add ir.rule and use the orm (opw 607782)
[FIX] base_action_rule: more flexible wrapper signature

Some objects (e.g. account.move.line) have a different signature than the classical 'cr, uid, ids, vals, context=None' and may add extra arguments.
This fix allows to create rules on these objects and still pass the valid arguments.
(opw 609204)
[REM] Bazaar leftovers...