[IMP] Rounding not necessary

Without this better floating point handling, an extra stock move might
be created for zero quantity for some order lines upon PO confirmation,
because qty is equal to something closer to e.g 1.14e-13, but this is
larger than 0, so it creates a stock.move, which gets rounded too late
to 0.0

Closes #3346

Fixes comparison with min_quantity orderpoint in scheduler - basic floating
point math issue in procurement scheduler when comparing current quantity
with orderpoint minimum quantity. In certain cases floating point comparison
could result in e.g 400.0 < 400.0 == True due to typical floating point
comparison issues, as Odoo doesn't use Decimal types where the issue
doesn't exist.

Fixes early exiting out of the loop cycle, in case qty is already near zero.
Fixes the new procurement creation check, to not do that if it's close
enough to zero already, to be considered a floating point math error, not
really non-zero.

These combined (or at least the last one) avoid each supply_method == buy
pending in draft PO's getting a zero quantity extra procurement order each
time the scheduler runs. Otherwise there could be hundreds of zero quantity
procurement orders pending, which makes the confirming of the PO take hours,
due to creating hundreds of stock moves for each order line.

Use float_compare helper to solve all these with floating point type for now,
instead of the more evasion possibility of converting to Decimal module.
Two potential bad comparisons remain, add FIXME notes for now until further
analysis.

Also: Float rounding on reste when comparing and on the procurement qty

Fixes #4011

[FIX] action_confirm was not asking for purchase pricelist, otherwise it was asking for sale pricelist

Needed to create filters like "previous month"

It was just defined for "datetime", but is also needed for "date"

closes #2915

This is related to rev. 83b28737

[IMP] Query should pass through orm and as such the refreshes can be removed in the code, which will go faster as it is done automatically by the new api

[IMP] Add a method half-up for uom conversion in case we want to convert from default UoM to something else + remaining_qty round + default factor on UoM

[IMP] When preparing pack operations, use the smallest UoM of the moves if they are smaller than the default UoM. Otherwise use default UoM.

The same is done when extra moves are generated.  It is going to check if the UoM of the operation is smaller if it has one.

Throw an error when a key can not be found in action_done because there were links on a move
that was not supposed to be done (e.g. 0.5 Dozen when Dozen is rounded at 1)

[IMP] Throw an error when a key can not be found because of UoMs/picking + extra float_compare

[IMP] Integrate remarks qdp

[IMP] Rounding should be done on move immediately to default UoM and quants should be rounded to the default UoM + remaining_qty

[FIX] Remaining qty should each time be in the default UoM of the product

Even with different UoM we want a consistent matching between moves and pack operations.
When calculating the remaining qty on move/pack operation we always start by converting the
qty on the move/operation to the default UoM and afterwards we subtract the links between them
which will also be in the default UoM of the product.
In order to create backorders / extra moves these quantities are used.

When a negative quant is created but the positive quant counterpart is reconciling
a negative quant that of course also has a positive counterpart, the latter should eventually
let its field propagated_from_id tell that it originated from the very first negative quant as the
second negative quant will have disappeared through reconciliation.

[IMP] No digits_compute on product_qty of move + rounding on qty_available fields + add float_compare

The find method returns a list of ids while the on_chage expects an int

[FIX] website_blog: Show tag by blog. No interest to display all tag, anyway the search by tag is done for the current blog

[FIX] account_analytic_plans: take analytic distribution into account when creating a move line from bank statement reconciliation

The backend would otherwise fail because the value has been already processed

Was caused by missing tags.
Also fix also backwards-compatibility for textext selection method.

[FIX] website_forum: restore bind to onclick because CKE Editor uses it, so on('click', fun) breaks things.

Fixes bugs with z-index error on some popups (image selector for example...)

This is to help forum moderators to fight against
spammers. It was previously difficult as the spammer
profile became unreachable as soon as their karma
went below 1, even if they had other questions
or answers still published.

It looks there is a bug in Firefox concerning responsive images in table. See bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=975632
Bootstrap advises to use width: 100% for .img-responsive as workaround were needed.
The @moz-document is to apply this for Mozilla only.

opw-617582
opw-618659

The field account_id was inherited with position="replace" meaning we erased
future changes made into hr_timesheet_sheet (41f2eba9 missed "type in []" and
65f31b90 missed use_timesheets).
Replace by position="attributes" to only change what matters: the on_change.
Fixes #3974

The website name is by default "localhost" (used in the page title in the format
"Current Page | Website Name") but there were no way to change it.
Fixes #3493

During rev. cbe2dbb6, type2journal was refactored, and set as a global variable in the top of the file, as it was use everywhere accross the file.
But, in this specific method _get_journal_analytic, this type2journal dict wasn't the same as everywhere else, as you can see at rev. d2ff95f6 for example. We must therefore set a specific type2journal dict for this specific method.

Reminder emails are generated based on the list of attendees.
The email_to field used to be a string with a list of emails separated by spaces
while the comma is the valid separator (RFC2822).
Fixes #3933 #3784 #2033

Button "Save and continue" was wrongly named as it worked only once the template
is not in edit mode (so already saved).
Hide the button to only get it in readonly mode and rename it for better
understanding of its purpose. (opw 614563)

Make sure a too long value in the subtotal will not overlap the form sheet
Fixes #3698

See issue #3964 for more detail.  Main problem was caused by commit
f0e331e0.  It set the key name+'__display' to false when reloading
a record for all field types, but it was only concerned with many2many.

Invoice control field was invisible, and we cannot change value if none selected or copy picking in.
Fixes #3636

Explicitly specifiy that quantities are in product uom

a blog will receive notifications only for published posts. They
will not receive all comments of all posts anymore.
When commenting a post users will receive the answers.

Added tests to try to test this behavior.

requested by fp. the filter is wrong and not very useful from a
functional viewpoint.