Monkeypatching is not a good practice, but it's in some cases necessary.
This is especiallly true when relying on third party modules.
Reasons may vary:

- to adjust for compatibility between versions
- to fix a small detail without reworking the external module.

In Odoo, there are several places in which monkeypatching is done.
This PR aims to put most of the monkeypatching together and to make clear at a glance which external modules are subject to it, and how.

Until now, the modules present here are of broad interest, and may belong to the `base` module.
There are cases in which a single Odoo module will require a third-party monkeypatched module that will get installed as `external_dependencies` in the `__manifest__.py` file.
We can leave the monkeypatching in that module, but we suggest using the `register` function here to make it at least visible at runtime, so that from the Odoo shell we can query them for troubleshooting:

```py
>>> from odoo.tools.monkeypatch import monkeypatches
>>> from pprint import pprint
>>> pprint(monkeypatches)
{'OpenSSL': <function monkeypatch_OpenSSL at 0x7fd7d8db3b50>,
 'PyPDF2': <function monkeypatch_PyPDF2 at 0x7fd7d8db3be0>,
 'xlsx': <function monkeypatch_xlsx at 0x7fd7d8db3c70>,
 'xlsxwriter': <function monkeypatch_xlsxwriter at 0x7fd7d8db3d00>,
 'xlwt': <function monkeypatch_xlwt at 0x7fd7d8db3d90>,
 'xmlrpc': <function monkeypatch_xmlrpc at 0x7fd7d8db3e20>}
```

All the monkeypatching will be done so that import <module> will already load the monkeypatched module.
Modules will have a new `<module>.__is_monkeypatched__` attribute set to True.
This will remove the need to import from odoo.tools.misc.<module> and also ensure that people not aware of the monkeypatching use the wrong version.

Community PR: https://github.com/odoo/odoo/pull/98996