A date filter (`<filter date="date_start"/>`) filters on a single field: the periods it offers, as well as the relative ones introduced in [1], match the records that *start* in the searched period.

For models describing a range rather than a single date, it is useful to be able to search for records that are ongoing during a given period.

A date filter can now name the field ending that span:

    <filter string="Period" name="period" date="date_start" end_date="date_stop"/>

Its periods and its relative options then match the records overlapping the searched period:

    ['&', ('date_start', '<=', period_end),
     '|', ('date_stop', '>=', period_start),
     '&', ('date_stop', '=', False), ('date_start', '>=', period_start)]

A record with no end date ends when it starts. Each bound is serialized with the type of the field it is compared to, so that a date field and a datetime field can be paired.

Task-6546268

[1] https://github.com/odoo/odoo/pull/267980

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Backport of https://github.com/odoo/odoo/pull/287446
which one is a Forward-Port-Of: https://github.com/odoo/odoo/pull/285915
because freeze v20 meanwhile

Several diff for OXP

[IMP] event: improve A4 foldable badge
-> required for oxp kenya - if you have ticket instruction, use it on badge + add qr code always visible

[IMP] event: don't show tag (question reply) if only one choice
-> fix case of "yes, agree" show on badge as tag "yes"
 
[IMP] website_event_track: typo and make it less verbose 
-> FP quick pass usability

[IMP] website_event_track: replace fa-bell by fa-star 
-> why ? not sure better after... but FP request
-> + add menu whishlist directly in event sub menu

## deploy

```
views = [
	'website_event_track.agenda_main_track',
	'website_event_track.track_card',
	'website_event_track.tracks_search',
	'website_event_track.event_track_aside_other_track',
	'website_event_track.track_widget_reminder',
]


from odoo.upgrade import util

for xmlid in views:
	util.update_record_from_xml(env.cr, xmlid)
```

Forward-Port-Of: odoo/odoo#285915

Forward-Port-Of: odoo/odoo#288790

**Problem:**
Searching on free_qty can be slow when there are many stock.move and stock.quant. The search method uses _compute_quantities_dict() to compute the free_qty based on stock.move and stock.quant, which is expensive.

**Solution:**
A similar field, qty_available, has a faster search method based on stock.quant only. This method can be adapted to support fast searching on free_qty by also aggregating the reserved_qty and subtracting it from the qty_available.

**Perf Table:**
Record: product.template, with ~20k stock.picking and most products w/o moves.

|Record count|Time before|Queries before|Time after|Queries after| 
|------------|-----------|--------------|----------|-------------|
|10k         |2.14s      |214           |370ms     |45           |
|50k         |6.06s      |644           |829ms     |50           |
|100k        |11.42s     |1196          |1.05s     |46           |

opw-6266096

Forward-Port-Of: odoo/odoo#287363
Forward-Port-Of: odoo/odoo#270434

Prior to this commit, the payroll dashboard could experience high latency 
during load times. This was primarily caused by the heavy use of `safe_eval` 
to compute Python-based warning actions (`evaluation_code`), as well as the 
rigidity of the `button_action` (Many2one) field which limited dynamic UI routing.

This commit refactors the warning action system to fix these performance 
issues and clear technical debt:
- Replaced the relational `button_action` field with a generic JSON-driven 
  `action_config` text field on `hr.payroll.warning`.
- Migrated all existing data records in `hr_payroll`, `l10n_be_hr_payroll`, 
  and `l10n_be_hr_payroll_account` to use `action_config`.
- Converted several Python-evaluated warnings into pure `domain` warnings 
  by moving static dictionary generation and `group_by` clauses into the 
  JSON configuration, allowing the backend to skip `safe_eval` entirely.
- Improved the separation of concerns: the backend strictly handles ORM 
  detection (`warning_domain`), while `action_config` handles UI routing.
- Set up the infrastructure to support volatile frontend context keys 
  (e.g., for autofocusing fields) without polluting the ORM context.

This commit improves the UI of appointment:

* To improve the readability of the "total_capacity_reserved" field in the records of the kanban view, its background color is lightened.
* The default alarm of the appointment type is set to 1 day.
* The name of the appointment booker is no longer used for the greeting in the confirmation email since it is not set if the appointment is done from the backend. Instead of it, the first of the attendees is used and if they do not exist, the organizer is used.
* The popover is improved. Margins are placed between the buttons in the footer, to avoid having them stuck to each other. A maximal width is set for the videocall_location field, this way it does not impact the size of the popover.
* To avoid a technical label, the default falsy label of CalendarEvent.resource_ids, which is "Undefined Attendee", is replaced by "Unassigned".

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

Task-6566639

Forward-Port-Of: odoo/enterprise#131840

mock- https://link.excalidraw.com/l/65VNwvy7c4X/1BoTHSkGUpa

- Added new warning on payroll dashboard for employees not having allocation.
  Doesn't apply to employees without contract and salary structure dirigeant.
- Added "Not defined" on employee form o-stat-value when there is no allocation.
- Added new button "Grant Time off" on employee Time Off dashboard only visible
  to time off managers and when no allocation. On click-> new allocation request
  form opens.
- Updated fields for New Allocation request form from Time Off Dasboard:-
   - Removed name field.
   - Rename "Ask for" to "Duration" for `number_of_day_display` field.
   - Change time type field to widget time type tags
   - New button "Grant" in place of "Submit Request" directly approves requests.
- Updated the popover form for Time off gantt:
   - Warning message on no allocation shows is in alert-danger class.
   - If there is no enough allocation then "Allocate & Add" appears which
     creates required allocations with leaves.

task-6476239