[IMP] mail, email_template: mass mailing feature cleaning
- now differentiates mass mailing and mass post.
- mass mailing is a true mass mailing
- using same_thread log a copy in the document, without using message_post
(using notification field, + model and res_id)
- improved form view of composer, adding a filed explaining a bit the various
recipients
- removed unnecessary fields coming from the template (partner_to, ...) because
they are confusing -> composer should be easier to understand and use
- removed some unnecessary code
- removed double body computation when using templates (one for tmeplate, then
the wizard -> not necessary)

This commit will be followed by other to try to improve the mass mailing
and mass post.
[MERGE] Sync with trunnk
[IMP] mail, email_template: still continuing work to improve performances of mass mailing.
main differences :
- record_name is not a function field anymore, but a char field + a method in create
if not given (default-like, but dependent of other values). This allows the composer
to give a value for record_name (False for email mass mailing) to avoid browsing
records and having their access rights issues in the way
- author_id, email_from coming from composer instead of called in every mail.message
creation
- moved code dealing with attachments from send_mail to get_mail-values, to that at
the end of this method we know all values of the email

Some tests have been updated / temporarily disabled.
[MERGE] Sync with trunk
[CLEAN] email_template: cleaned modified code to lessen the diff
[CLEAN] mail: some code cleaning in the modifications
[REF] [ADD] marketing: marketing config + CRM-related stuff module reordering
- marketing module now holds only the basic stuff for marketing related
modules: mainly marketing settings + menu definition
- marketing_crm new module is a bridge between crm and marketing and
holds the crm-related stuff previously present in marketing module.
[MERGE] Sync with trunk
[IMP] [REF] mass_mailing: first draft for the saas-4 refactoring.
Improved mass mailing form view, that is used as a central point to create new
mailings.
Added concept of contact list (based on partner, or leads (to add)), as well as
contact (a list of name / email to import). Mailings are done un contact list
to simplify the way it works.
Added a kanban view of templates, with a flag to filter only mass mailing templates
(to avoid havign to deal with acknoledgments).
Using campaigns is now an option (a group), mailings can be done without having to
deal with campaigns.
Mailings and campaigns now have a status, used to display their kanban view.
[MERGE] Sync with trunk
[MERGE] Merged prototyping branch about improving performances
in messaging, especially for mass mailing and mail mail creation. Some things will
probably be discarded or improved further, but this work will serve as a basis
for the whole mass mailing refactorign about speed.
[REM] mail_message: removed dead code
[REM] mail_message: removed dead code: quote context is not planned
to be used anymore.
[IMP] mail_message: avoid doing search criterions on subtype_ids, takes long time
[CLEAN] mail_mail: lean cleaning
[IMP] mail.compose.message: removed unnecessary code, email_from is already corretly managed
[MERGE] Sync with trunk
[IMP] [REF] mail_compose_message: slightly cleaned wizard code to lessen the number of corner cases and
to remove unnecessary code.
post and filter_id fields have been removed as they are not necessary.
Updated tests accordingly to new mass mailing tests: mass mailing create
emails, no message_post anymore using followers.
[IMP] mail_compose_message: added is_log boolean field for internal notes; + removed context hack that
did the same thing. Fixed composer form view: internal note, only subject + body is
displayed.
[FIX] mail_compose_message: create Re subject only when having a parent