16.0 pms long stay

[DarioLodeiros]

This pull request introduces the new "PMS Long Stay Reservations" module, which adds comprehensive support for managing long-stay bookings in the PMS system. The module enables reservations to be automatically split into weekly or monthly segments, each managed as an independent reservation but linked together for cohesive management and billing. It extends core models, introduces new configuration options, and seamlessly integrates with existing PMS pricing and service logic.

CAUTION:
This PR need some changes in PMS base: OCA/pms#364

Key features and changes include:

Long Stay Reservation Functionality:

• Added a new reservation type (long_stay) to pms.reservation and pms.folio, enabling the creation and management of long-stay bookings. When such a reservation is created, it is automatically split into weekly or monthly segments, each represented as a separate reservation and linked via a new long stay group. Each segment also receives an automatically generated service line for billing, with the timing configurable on the property. [1] [2]

Configuration and Model Extensions:

• Extended pms.property with new configuration fields: week_start_day (to define the start of the week for splitting) and long_stay_billing_timing (to control when the service is invoiced for each segment).
• Extended pms.room_type and product_template (via imports) to support long-stay specific configuration, such as period type and dedicated products.

New Data Models:

• Introduced the new model pms.reservation.long.stay.group to group and reference all reservation segments belonging to the same long-stay booking. This model stores period type, original check-in/out, and links to all related reservations.

Module Metadata and Documentation:

• Added a module manifest (__manifest__.py) detailing dependencies, authorship, and data files, and a comprehensive README explaining the purpose, usage, and configuration of the module. [1] [2]

Module Initialization:

• Added __init__.py files to ensure all new models and extensions are properly loaded when the module is installed. [1] [2]