Reduce the number of goals that are recomputed. Remove the goals for users that
did not connect since the last update.
Add sql query for faster lookup and restrict on user table

When the cron is running on a database with a large number of goals (e.g. website_forum with thousands of users), it's possible the CPU time is exceeded and we may have a rollback after sending some emails (for granted badges).
To avoid sending twice emails, commit in cron mode after each reward.

Otherwise, this is no more possible to delete users having badges

Otherwise, this is no more possible to delete users with gamification goals

Indeed using fromkeys with a list / dict as argument leads to the creation
of shared list / dict. This could create some ugly side effects when
used in loops. This commit fixes or cleans this kind of statement to avoid
unwanted side effects.

Challenge
- 'Reward as soon as every goal is reached' box checked by default (most of the time people want this behaviour, few special cases were do not)
- Click on challenge kanban opens goal list instead of challenge form
- Add button 'Start Challenge' clicking on statusbar is not intuitive

Badge
- When creates a challenge from badge view, set by default badge to 'For Every Succeding User' field
- replace filter 'Current' vs 'Passed' by 'Running' (in progress and done with not reached end date) vs 'Done' (done & failed without end date or end date passed)

Goal
- list of badge on employee form not the first tab

On a large database, thousands of badges may have been granted. This code used to prefetch all fields of the users and badge users. This was highly inefficient. Replace this code by SQL query.

Due to the multi-company record rule on gamification.goal,
each access to the Goals menu and each opening of the
Messaging menu (thus calling get_serialised_gamification_summary())
is extremely slow (with several thousands goals/users).

Adding auto_join to the user_id FK on goals makes it much
faster. However it causes crashes when reading the table
because the _order of gamification.goal uses `create_date`,
which becomes ambiguous after the auto_join with res_users.

Solving this can be done by re-implementing _read_flat()
in the ORM using the internal Query object, as in search(),
which takes care of fully-qualifying all column names.

Until this is fixed, a simple workaround is to use
start_date in the _order instead of collision-prone `create_date`.

Closes #1536

A squashed merge is required as the conversion of the apiculture branch from
bzr to git was not correctly done. The git history contains irrelevant blobs
and commits. This branch brings a lot of changes and fixes, too many to list
exhaustively.

- New orm api, objects are now used instead of ids
- Environements to encapsulates cr uid context while maintaining backward compatibility
- Field compute attribute is a new object oriented way to define function fields
- Shared browse record cache
- New onchange protocol
- Optional copy flag on fields
- Documentation update
- Dead code cleanup
- Lots of fixes

    ' 'str' object has no attribute 'strftime' '

gamification: when changing the domain on a goal definition give a simple check to avoid getting a traceback when the challenge is reloaded

The read_group behaviour has changed and read_group no longer sum on the field you are grouping.
Instead agregate on the field we want to sum and use no groupby.
For future version, grouping on a user such as what is done in batch mode is a better way to process.

[IMP] gamification: avoid fetching function field while we could reuse the cache system of the browse records (avoid memory errors when updating a large number of records)

[FIX] gamification: make sure than a cron running more than once a day will not report the progress more than once

bzr revid: mat@openerp.com-20140512092718-s6143ajy2g18ofy4

[FIX] gamification: avoid challenge to be initialised at the target limit (e.g. set your company data goal has a target of 0) and make sure we will compute the goal at least once

bzr revid: mat@openerp.com-20140509131839-lm5zt696sif1krvx

[IMP] gamification: avoid subscription hacks and send directly relevant messages to followers of the challenge, remove the goals of users not matching the user domain anymore

bzr revid: mat@openerp.com-20140507095616-1xvetgj4qel7iqii

bzr revid: mat@openerp.com-20140506143834-od28gkhbpbhsgde4

bzr revid: mat@openerp.com-20140506135953-3hssq2lycvy1c3df

bzr revid: mat@openerp.com-20140506134805-4nsurv82cg9anfvm

[FIX] gamification: be sure that not challenge get subscribers depending of the report_message_frequency

bzr revid: mat@openerp.com-20140506115245-ktuxhcsml466ym6u

bzr revid: mat@openerp.com-20140506113831-iut3aqbwfwbnertv

[IMP] gamification: move write in goal update inside the first loop to be able to group the computation by definition (and potentially apply intermediate commits)

bzr revid: mat@openerp.com-20140506112109-z4rsx5umet5x6n26

bzr revid: mat@openerp.com-20140506102942-obopc9j5a2136cxh

Removing the inheritance to mail.thread will avoid posting message at creation and other tracking mechanism at each write. Updating a challenge with a large number of users will be significantly faster.

bzr revid: mat@openerp.com-20140506093716-xvpe1n2ase2zix0v

[FIX] gamification: do not set a start_date by default as the cron starts past challenges (making data challenge to start) and avoid useless write

bzr revid: mat@openerp.com-20140424110341-pnu79q44m7gzl8t0

bzr revid: mat@openerp.com-20140422075247-5rddurvr6ymt80mo

bzr revid: mat@openerp.com-20140418163837-32nldgj5u04q9kyu

bzr revid: mat@openerp.com-20140418163440-7y1k3sliuk9bgco8

Needs server fix to avoid sending evaluated data.

bzr revid: mat@openerp.com-20140418161053-lc970koh96wfe200

bzr revid: mat@openerp.com-20140418150618-9g179rleuru44xrt