The timesheet creation helper for project tasks has been moved fully into the Timesheet Grid app, where the related timer functionality now lives. This keeps the app structure aligned and avoids maintaining the same logic across separate timesheet modules.

Since the timer has been moved to timesheet_grid, we did forget to move the `project.task.create.timesheet` wizard as well.
At this time, the model is still created in hr_timesheet and overridden in timesheet_grid.

so in this task completely move the wizard to timesheet_grid as it is no more used in hr_timesheet.

task-2710154

Steps to reproduce: - With mexican accounting, as a user with 'Billing' right - Create an invoice, and confirm it Issue - AccessError The reason is the attachment is created at the installation of l10n_mx_edi with res_company._load_xsd_attachment, then create_uid == 1 (System) but in ir_attachment we check if create_uid == self.env.uid which is the id of the user. Add a sudo to grant acces to the user opw-2724099 Please enter the commit message for your changes. Lines sta

Steps to reproduce:

- With mexican accounting, as a user with 'Billing' right
- Create an invoice, and confirm it

Issue

- AccessError

The reason is the attachment is created at the installation of
l10n_mx_edi with res_company._load_xsd_attachment, then create_uid == 1 (System) but in ir_attachment we check if create_uid == self.env.uid which is the id of the user.

Add a sudo to grant acces to the user

opw-2724099

 Please enter the commit message for your changes. Lines starting

Forward-Port-Of: odoo/enterprise#23242
Forward-Port-Of: odoo/enterprise#23233

When the cron to send the followup report ("Account Report Followup; Execute followup") is triggered, the email with the followup report sent might not reflect the followup level set in the database. For example, if you rely only on automatic followup without checking the follow-up report in the interface, the system will send emails only with the message of the 1st followup level. The option 'keep_summary' is set by default when we call the send_email() function. This will keep the last

When the cron to send the followup report ("Account Report Followup; Execute followup") is triggered,
the email with the followup report sent might not reflect the followup level set in the database.
For example, if you rely only on automatic followup without checking the follow-up report in the interface,
the system will send emails only with the message of the 1st followup level.

The option 'keep_summary' is set by default when we call the send_email() function. This will keep the
last summary set in the report manager. This is ok if we use the interface to send mail because the summary
is updated to the one of the current followup level when loading the followup report page. In the case of
the schedule action (which uses the same function to send mail), this is not because it might sent an
outdated mail (with different amounts/invoices/dates).

This commit removes the default 'keep_summary' = True and set this parameter when we click on the button
"Send by mail" in the follower. So if the cron is triggered it will recompute the summary (mail message)
based on the followup level.

opw-2667996

Forward-Port-Of: odoo/enterprise#23104