By default, the longPressDelay is 1000ms which is not intuitive
and makes it pretty much unusable in touchscreen devices.

In this case, it makes no sense to have a delay for selecting dates.
By setting it to 0 we're effectively disabling the pressDelay, and
the user experience is much better.

* Print event.registration receipts.
* Refunding a pos.order will cancel the event registrations.
* Support pricelists.
* Refactored code for better overrideability.

This allows to play nice with other modules, that may either be:

* Trying to modify the created registrations
* Creating registrations themselves
* Or even calling `_create_event_registrations` programatically.

It has no impact on functionality, though.

There was a typo on the xml view, having it not rendering properly.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: pos-15.0/pos-15.0-pos_event_sale
Translate-URL: https://translation.odoo-community.org/projects/pos-15-0/pos-15-0-pos_event_sale/

Currently translated at 100.0% (69 of 69 strings)

Translation: pos-15.0/pos-15.0-pos_event_sale
Translate-URL: https://translation.odoo-community.org/projects/pos-15-0/pos-15-0-pos_event_sale/it/

It helps understand the difference between `getSeatsAvailable` and
`getSeatsAvailableReal`. Moreover it helps with the module extensibility.

Currently translated at 100.0% (69 of 69 strings)

Translation: pos-15.0/pos-15.0-pos_event_sale
Translate-URL: https://translation.odoo-community.org/projects/pos-15-0/pos-15-0-pos_event_sale/it/

… pos_order_line before installation

This helps to avoid a Memory Error when installing this module on an instance with a big amount of existing pos_order_line

…ray of ids

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: pos-15.0/pos-15.0-pos_event_sale
Translate-URL: https://translation.odoo-community.org/projects/pos-15-0/pos-15-0-pos_event_sale/

When paying a `pos.order`, confirm only the `event.registration` that are
in draft state. Don't attempt to confirm the ones that are already confirmed,
nor the ones that might be cancelled.

If we cancel a `pos.order`, we should cancel the related `event.registration`(s)
However, if the `event.registration` is already done, we should not cancel it
as it would be already too late to do so.

Registrations created from the PoS are not to be confirmed automatically.
We confirm them when the `pos.order` is paid, but they are to remain in `draft`
until then.

In the PoS, if the order is not paid, then it's not confirmed.
If it's not confirmed, then we might as well ignore it. We shouldn't
cancel any existing registrations until then.

Negated lines are particularly useful with PoS modules that disable the removal
of pos orderlines through the use of ``disallowLineQuantityChange``.

This is the case of `l10n_fr_pos_cert` module, for example. But there are other
core modules doing it, too.

In this case, added order lines can't be removed. Instead, the cashier is
encouraged to add a negative to 'cancel' the original one.

e.g.:

Adds a line with 10 tickets.
Then, adds a line with -10 tickets.

This should be almost the same as removing the first line: no actual
registration should be confirmed in the end, as we're reverting this sale.

Moved some ORM tests to `tests_backend`, that will execute faster than tours.
Added unit tests to cover more backend scenarios.

EventEventTicket inherits from EventTypeTicket, so we don't need to duplicate the field declaration, if it is the same in both module. This ease overriding, as we need to override only one model, if we expect the same behavior in both.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: pos-15.0/pos-15.0-pos_event_sale
Translate-URL: https://translation.odoo-community.org/projects/pos-15-0/pos-15-0-pos_event_sale/

Currently translated at 100.0% (73 of 73 strings)

Translation: pos-15.0/pos-15.0-pos_event_sale
Translate-URL: https://translation.odoo-community.org/projects/pos-15-0/pos-15-0-pos_event_sale/it/