[IMP] l10n_mx_*: provide different account for credit notes

modules: l10n_mx_reports, l10n_mx_edi, l10n_mx_edi_pos
When handling credit notes for accounting purposes it's not correct (or
even legal in mexico) to use the same account for anything related to
credit notes (discounts, bonuses or returns). Instead, all of these are
accounted for in a different account that reduces the sales but also
tell us how much of the sales were reduced by this account.

This commit provide an account for these cases, and make it customizable
for the user to set the account he wants (with a setting in the 'Default
Accounting' section). Also, POS returns are now associated with this
account.

A second account is created to handle the "re-invoicing" concept: when a
pos order is done and the session is closed, if the customer wants to
self-invoice the system perform a reversal of the session and create 2
new invoices, 1 for the customer and 1 for all other orders from the
original session. The new account is associated to the debit lines of
the reversal (not vat), the credit lines of the customer invoice (not
vat)

Task-4576187

During the [rework of the follow-up report][1], we removed the "No Follow-Up" field from journal items, making it impossible to exclude individual journal items from triggering a follow-up.

In the related community commit, we re-introduce a field for that, since it is a common requirement to be able to exclude individual items from the follow-up reports.

In this commit we do the following:
1. Adapt the Follow-Up Report and Customer Statement variants of the Partner Ledger to add a toggle for the "No Follow-Up" field on each report line, that toggles the field on the corresponding journal item(s).
2. Prevent the follow-up status on the partner to change when all of the overdue journal items are marked as "No Follow-Up".
3. Make sure users can toggle the "No Follow-Up" setting on the invoice level when opening the "Overdue Invoices" view from the partner's "Accounting" tab.
4. Make sure all receivable/payable lines without a due date (either from a manual miscellaneous entry or a PoS entry) are put under the "Due" section is the Follow-Up Report instead of the "Overdue" section. Since there is no due date, they can't be overdue.

[1]: https://github.com/odoo/odoo/commit/67dc71588751c9f115e09959d774686c2207a1f9

[task-4632300](https://www.odoo.com/odoo/project.task/4632300)

Related to https://github.com/odoo/odoo/pull/203329

Due to an issue with the `CameraInterface`, the same identifier would be chosen for any connected camera (`camera-2`), meaning only one camera could be used at once.

To fix this, the `camera.id` property is used as the identifier instead. The `libcamera` documentation says the following:

> The camera ID is a free-form string that identifies a camera in the
> system. IDs are guaranteed to be unique and stable: the same camera,
> when connected to the system in the same way
> (e.g. in the same USB port), will have the same ID across both
> unplug/replug and system reboots.

However, we will also still return the last camera with the `camera-2` identifier, so that existing device configurations in the backend don't get lost. In master we will remove this legacy identifier. You can see the legacy camera with the others in the list below:

<img width="801" height="385" alt="image" src="https://github.com/user-attachments/assets/6f3a6408-bcb4-46b0-980e-b5a8881f6df0" />


In addition, another small fix was made to the `CameraDriver` to ensure a string is sent rather than raw bytes, this prevents a traceback when communicating over the websocket.

task-4792552

Forward-Port-Of: odoo/enterprise#93076

### Steps to reproduce:
	- Set Marc Demo's contract work entry source to attendances and working schedule to flexible hours.
	- Create a public holiday with generic time off work entry type.
	- Create one or multiple attendances for marc demo on the public holiday.
	- Regenerate work entries for marc demo for that day, the gaps in between the attendances created and the working hours will be filled with work entries with the right start/end time but duration will always be 8h.

### Cause:
This is happening because when getting the duration batch for the work entry we get the attendance intervals the employee should work in that period and if the employee is flexible we will get a fake attendance with the number of hours required per day ignoring if the period is just a small period of the day

### Fix:
We are checking now since the start date not monday so we don't set a fixed week start. We check if the period is less than the remaining hours we get it as it mostly means that it is less than one day

opw-4887933

Forward-Port-Of: odoo/enterprise#92519
Forward-Port-Of: odoo/enterprise#90163

**Steps:**
- Install the hr_referral and hr_recruitment modules.
- Open a referred applicant from the Recruitment module.
- Create a new stage and place it before the applicant’s current stage.
- Move the applicant back to the newly created stage.
- Open the Referral view for the referring employee.

**Description of the issue/feature this PR addresses:** 
Even though the applicant is moved back to a newly created stage, the referral view still shows the previous (later) stage as completed. The new stage is not reflected, leading to incorrect stage tracking in the referral module.

**Cause:**
The `use_in_referral` field in the `hr.recruitment.stage` model controls whether points are updated for a stage. Stage checkbox in the referral view depend on these points.

**Fix:**
This PR updates the logic to:
- Allow stage point updates even when the applicant moves back to a previous stage.
- Ensuring that points are awarded for all use_in_referral stages skipped when jumping from one to any non-referral stage.
- Ensure that points are added or removed properly and even sending notification based on the `use_in_referral` field.

task-4968602