- Merge `set_lot_confirm_action` and `set_lot` endpoints so as to call only one endpoint
- Ensures lot is not created in DB until proven valid
- Add expired expiration date check

Update the 'set_lot' state logic to store user input locally on the
active move line before calling the backend.

Crucially, this ensures the 'set_lot' function is now called with both
'expiration_date' and 'lot_name' at the same time upon confirmation.
This prevents premature backend calls with partial data and allows
for better validation of the lot on the server.

Add an endpoint to call on lot name scan. This enables to detect already existing lots.
This endpoint could also be used to add logic to extract extra infos from barcode such as expiration date.

…t name scan

…icker component

…t name scan

Refactoring ideas in: OCA@3469638 and OCA@c5f931b

When a user provides a lot name but forgets the expiration date, the `lot_name` was previously lost
in the response.

This change ensures that `lot_name` is included in the returned
data, allowing the UI to retain the value and
preventing the user from having to re-type it.

The frontend was sending expiration dates in the user's local timezone. Because Odoo expects datetime values in UTC, this caused "hour shifts" that could move the expiration date to the previous day in the database.

This fix ensures that the selected date is treated as local midnight and converted to the corresponding UTC timestamp before being sent to the server.

…display

Updated the lot expiration display to show only the date component. Since the selection widget is restricted to dates, displaying the time was redundant.

…on date

…-input code from OCA#1132

…trings

- Rename internal methods to follow standard naming conventions, ensuring compatibility for downstream modules inheriting from this component.
- Updated docstrings to accurately reflect method behavior.

Enforce the 'use_create_lots' setting from the picking type during the
reception process.

… screen

The logic for the cancel action was defined, but the event listener
was missing from the button template.

…transitions

When a lot name is present on the move line, the system now attempts to find a matching existing
lot record. If found, the lot metadata is sent to the frontend to
pre-fill the screen, preventing redundant data entry.

Update '_response_for_set_lot' to check if lot information was already
resolved during parsing. If the parsed data is complete, the system now
bypasses the 'set_lot' entry screen and processes the confirmation
automatically.