To reproduce:
 1. Sync the IoT with a 17 database
 2. Once it is set up, force shut down the server by Ctrl+C 2 times
 3. Wait a few seconds:
=> crash of `WebsocketClient` thread with the following traceback:
```
Traceback (most recent call last):
  File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_i>
self.run()
  File "/home/pi/odoo/addons/hw_drivers/websocket_client.py", line 83>
self.ws.run_forever()
  File "/usr/local/lib/python3.11/dist-packages/websocket/_app.py", l>
raise WebSocketException("socket is already opened")
websocket._exceptions
WebSocketException
socket is already opened
```

The IoT synchronised servers can stop in 2 ways that we need to handle:
 - Gracefully (Ctrl+C):
  In this case a disconnection signal is sent to the IoT-box
  The websocket is properly closed, but it needs to be established a new connection when the server will be back.
  Solution: `while True` loop as `run_forever` will return on close. `time.sleep` for the reconnection delay

 - Forced/killed (Ctrl+C 2 times):
  In this case there is no disconnection signal received
  Solution: use `reconnect` that will automatically take care re-attempting a connection

  This will also happen with the graceful quit as `reconnect` will trigger if the server is offline while attempting the new connection

In both case, we perform a reconnection attempt with a delay of 10 seconds to avoid spamming the database


After this commit:
 The websocket will reconnect itself automatically after 10 seconds if the connection is disrupted

opw-3612528

Versions:
---------
- 17.0+

Steps to reproduce:
-------------------
1. Go to Project / Configuration / Projects;
2. create a new project;
3. set a Planned Date.

Issue:
------
Date picker closes after selecting a date while leaving the field empty.

Cause:
------
The `daterange` widget checks on changes whether the dates are a range using a `isRange` method. Before https://github.com/odoo/odoo/pull/125039, this was true for any array, after it is only true if the date field has a related field to form the range, and if the field is required or neither field is empty.

For project, this still worked because it had *a* `required` attribute for the date field, but https://github.com/odoo/odoo/pull/143509 changed this so that it only counts as required if the given expression evaluates to a non-falsy value.

For project, the date fields are only required if one of two dates has been given, but an `onChange` method clears both fields if only one is given, which makes it impossible to select any date, as the date picker doesn't allow you to pick a range, and the `onChange` method clears any selected date because it's not a range.

Solution:
---------
Add a `force_range` option to the `daterange` widget to force range selection. This would make sense in models like `project.project` that take either 0 or 2 dates, but cannot force the 2 date requirement based on another field.

Also modify `project.project`'s `onChange` method to not clear the `start_date` if no end `date` is given. This change alone allows the user to enter dates again without updating the `project` module's XML files, but with the minor annoyance of having to open the date picker twice to select a range.

opw-3644238

This issue occurs when a customer creates multiple companies. Then, after installing the attendance module, after selecting the kiosk mode, an error is generated. This is because, before installing the attendance module, if the customer created a company, a single kiosk key is generated. This key is different for each company, but it is the same.

step to reproduce-
- First created two company.
- Install the `Attendances` & Open it.
- Click on the Kiosk Mode from Menu.
- Error will be generated.

sentry traceback-
```
ValueError: Expected singleton: res.company(2, 1, 4, 3)
  File "odoo/http.py", line 2157, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1732, in _serve_db
    return service_model.retrying(self._serve_ir_http, self.env)
  File "odoo/service/model.py", line 133, in retrying
    result = func()
  File "odoo/http.py", line 1759, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 1873, in dispatch
    return self.request.registry['ir.http']._dispatch(endpoint)
  File "addons/website/models/ir_http.py", line 235, in _dispatch
    response = super()._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 207, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 722, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/hr_attendance/controllers/main.py", line 82, in open_kiosk_mode
    } for e in request.env['hr.employee'].sudo().search_read(domain=[('company_id', '=', company.id)],
  File "odoo/fields.py", line 5118, in __get__
    raise ValueError("Expected singleton: %s" % record)
```

after this commit,Each attendance kiosk key generated during the company's creation is unique.

sentry-4617967282

Steps
=====
- Install module project
- Open the form view of a project
- Set a planned date
- Click anywhere on the page to remove the focus from the date picker

Issue
=====
The chosen date disappeared without any explanation to the user

Cause
=====
odoo#123268 introduced some changes related
to the planned dates of projects.
1. the write method is modified to avoid the write of only a start/end date (both date should be set or none of them)
2. a required is added on the start date field in the form view of project
3. an onchange is added to avoid to have one of both field set and not the other

This last change is problematic as it overrides the required behavior of the date fields.

On top of that, https://github.com/odoo/odoo/pull/143509 changed the behavior of the datepicker widget that only display the full range by default if both fields are required (which is not the case here if they are empty).

The combination of those changes have the consequence that the planned date field is unusable in the form view of projects.

Fix
===
The onchange being only useful in form view, it is deprecated as the required attribute is sufficient for this use case and provide the user warnings if he forget a field. On top of that a required attribute is also set on the end date field.

task-3628069

When the user copies an article, the system copies the body of the article 'as-is' without updating the ID references stored within it. As a result, the embedded views of article items stored in the body of the copy will list the article items of the original article and not its own article items.

This PR will address that issue by updating the context of the embedded views stored in the body of the copy. It will ensure that the embedded views listing the article items of the original article will now list the article items of the copy.

Steps to reproduce the issue:
1. Create an article
2. Insert an embedded view of article items (with /kanban or /list)
3. Insert a few articles
4. Create a copy of the article (using the "Create a Copy" button)

=> The embedded views of article items list the article items of the original article.

TO BE: The embedded views of article items should list the article items of the newly created article.

task-3349324

Forward-Port-Of: odoo/enterprise#49903
Forward-Port-Of: odoo/enterprise#42936