Currently, an error is generated when run 'Mail: Fetchmail Service' scheduled action.

Step to produce:

- Install the 'l10n_cl_edi' module.
- And manually trigger the 'Mail: Fetchmail Service' scheduled action.

Stacktrace

```
TypeError: FetchmailServer.fetch_mail() got an unexpected keyword argument 'raise_exception'
  File "odoo/tools/safe_eval.py", line 383, in safe_eval
    return unsafe_eval(c, globals_dict, locals_dict)
  File "ir.actions.server(128,)", line 1, in <module>
  File "addons/mail/models/fetchmail.py", line 186, in _fetch_mails
    return self.search([('state', '=', 'done'), ('server_type', '!=', 'local')]).fetch_mail(raise_exception=False)
ValueError: <class 'TypeError'>: "FetchmailServer.fetch_mail() got an unexpected keyword argument 'raise_exception'" while evaluating
'model._fetch_mails()'
  File "odoo/addons/base/models/ir_cron.py", line 388, in _callback
    self.env['ir.actions.server'].browse(server_action_id).run()
  File "home/odoo/src/custom/trial/saas_trial/models/sentry.py", line 33, in run
    res = super().run()
  File "odoo/addons/base/models/ir_actions.py", line 972, in run
    res = runner(run_self, eval_context=eval_context)
  File "odoo/addons/base/models/ir_actions.py", line 802, in _run_action_code_multi
    safe_eval(self.code.strip(), eval_context, mode="exec", nocopy=True, filename=str(self))  # nocopy allows to return 'action'
  File "odoo/tools/safe_eval.py", line 397, in safe_eval
    raise ValueError('%s: "%s" while evaluating\n%r' % (ustr(type(e)), ustr(e), expr))
```

The issue arises during the execution of the 'Mail: Fetchmail Service' scheduled action because the 'fetch_mail()' method call without argument, as we can see at [1], And this argument is added from this PR https://github.com/odoo/odoo/pull/152637.

link [1]: https://github.com/odoo/enterprise/blob/ba99dd4c236353c43376210a9aabcb0af5bd0299/l10n_cl_edi/models/fetchmail_server.py#L51

To resolve the issue, Add a default keyword argument at [2] to prevent an issue.

link [2]: https://github.com/odoo/enterprise/blob/ba99dd4c236353c43376210a9aabcb0af5bd0299/l10n_cl_edi/models/fetchmail_server.py#L51

sentry-5284073241

HOW TO REPRODUCE:
=================

- website_helpdesk_forum addon shall be installed
- Do not login (navigate as a public user)
- Go to the Website > Forum > Help > any post
- Double-click anywhere in the post body or select some text
- You should get the following client error from `OdooEditor._updateToolbar: Cannot read properties of null (reading 'classList')`

HOW TO FIX:
===========

By ensuring the wysiwig toolbar unlink button is present in the page before adding classes to it.

The bug seems to be in relation to the following PR odoo/odoo#147919, where the `OdooEditor._updateToolbar` method is slightly modified to ensure the toolbar unlink button is not visible initially, but forgets to check whether the element exists before hiding it.

The bug can be spotted when `website_helpdesk_forum` is installed as it sets to 0 the level of karma required to answer a post while keeping the full edit rights (image and link) to 30 pts. As a consequence, the WYSIWYG is included in the post page even when requested by the public users, but the WYSIWYG toolbar does not include the unlink button.

task-3932751
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr