[FIX]:Add noupdate in project data
[IMP] when selecting filter 'To Pay', also display the expense which is in Waiting Payment' state
[FIX] Restore the appropriate accounts on tax ACH-19.6
[FIX] */report: font names are case sensitive
[FIX] account,account_followup,l10n_{ch,es,pt,us,ve}: correct or remove wrong fields in <record> creation
[FIX] survey/report: correct style name
[FIX] sale/edi: do not import non-existing field date_planned
[FIX] document: even deprecated models need access rules (avoid warning)
[FIX] base_action_rule: even test models need access rules (avoid warning)
merge upstream
[IMP] stock: do not use assert in (python) tests
[FIX] stock: mute orm logger before checking access rules
[FIX] stock: mute orm logger before checking access rules
[FIX] l10n_mx: account.chart.template does not have any property_stock_account_{in,out}put_categ fields
[FIX] sale_stock: procuremenr.order object does not have a `property_ids` field. This field is added by `mrp` module, which we do not depend of.
[FIX] procurement: magic bypass transition was incomplete and preventing pulled flows from working

The procurement workflow has a magic `bypass` transition
that acts as a fallback for MTO procurements in case the
necessary modules are not (yet) installed. For example
it will consider a MTO+Buy procurement directly satisfied
if the Purchase module is not yet installed.
However this bypass transition did not properly take
"internal pulled flows" into account, which are added
by the `stock_location` module as a third kind of procurement
type. In this case the bypass would match and never
give stock_location the chance to run.
In order to be consistent with the other procurement
methods, the bypass transition needs to be adapted.

Also updated the check_move() method to make it more
explicit rather than a side-effect.
[FIX] procurement: magic bypass transition was incomplete and preventing pulled flows from working

The procurement workflow has a magic `bypass` transition
that acts as a fallback for MTO procurements in case the
necessary modules are not (yet) installed. For example
it will consider a MTO+Buy procurement directly satisfied
if the Purchase module is not yet installed.
However this bypass transition did not properly take
"internal pulled flows" into account, which are added
by the `stock_location` module as a third kind of procurement
type. In this case the bypass would match and never
give stock_location the chance to run.
In order to be consistent with the other procurement
methods, the bypass transition needs to be adapted.

Also updated the check_move() method to make it more
explicit rather than a side-effect.
[REVERT] stock: commit 9557/OPW 600078 assumes that production lot are guaranteed to be set on each relevant move

This assumption is incorrect in OpenERP v7. The WMS
design in OpenERP 7 and previous versions only permits
tracking production lots (aka serial numbers) on
incoming moves, outgoing moves and production moves.
You can specify production lots on internal moves too,
but the system will also generate internal moves for
many reasons, and nothing guarantees that they will
have the right lots assigned.
This is a design decision, and this means that we
must never enforce the availability of specific
production lots.

This features will be available in OpenERP 8 through
the use of an extra concept called "Quants", that
will make this kind of tracking possible.
[REVERT] stock: commit 9557/OPW 600078 assumes that production lot are guaranteed to be set on each relevant move

This assumption is incorrect in OpenERP v7. The WMS
design in OpenERP 7 and previous versions only permits
tracking production lots (aka serial numbers) on
incoming moves, outgoing moves and production moves.
You can specify production lots on internal moves too,
but the system will also generate internal moves for
many reasons, and nothing guarantees that they will
have the right lots assigned.
This is a design decision, and this means that we
must never enforce the availability of specific
production lots.

This features will be available in OpenERP 8 through
the use of an extra concept called "Quants", that
will make this kind of tracking possible.
[FIX] stock: stock.picking.in/out (technical models used to separate several picking types) should also apply _defaults from stock.picking