PURPOSE

Improve Online Events feeling, user experience and management for
event users.

SPECIFICATIONS

Allow multiple tries & improve layouts of track quizzed. Purpose is to add
feedback and allow to repeat quizzes, making them more fun to use.

Add a popover on the exhibitor cards giving their information. Purpose
is to improve they way exhibitors are displayed and ease their dicovery.

Improve track management through stage legend, like what is done in
project for example. Add customizable legends on stage kanban state,
track it on tracks records.

Update the track stage visibility logic. Rules are now

  * a published track is always displayed in agenda, tracks list and page
    view, whatever its state;
  * a track in a 'is_visible_in_agenda' stage (replacing 'is_accepted') is
    always displayed in agenda and tracks list. Its page view access is based
    on ACLs: aka: published = everyone, unpublished = for event users only;
  * a track in a 'is_fully_accessible' stage (replacing 'is_done') is
    automatically published when entering this stage, allowing its full
    display

Page view still relies on ACLs, and therefore on published flag automatically
set when entering "fully accessible" stage.

See sub commits for more details and explanations.

Task-2504216

// Commit 1
[IMP] account: Refactor tax group widget with OWL 

Refactor the tax group widget with the new JavaScript Odoo Framework:
OWL. This widget has 2 different components, one representing a tax group
and one representing the list of tax groups.

Task ID: #2312900
Initial Task ID: #1986412


// Commit 2
[IMP] account: allow mixing cash basis and non-cash basis taxes on the same line

The tax_exigible field of account.move.line made it impossible to mix 'on_payment' and 'on_invoice' taxes on the same invoice line, as the base line couldn't be be tax exigible and non-tax exigible at the same time. However, this use case is needed by some countries in order to implement withholding taxes.

To solve that, we totally remove the tax_exigible field from account.move.line and instead compute it on the fly with a domain (also passed to the query_get for SQL queries). An 'always_tax_exigible' stored computed field is also added on account.move, in order to still allow (like before) putting cash basis taxes on a miscellaneous operation without any payable/receivable line and still see it become exigible without needing any payment.

[IMP] account: improve cash basis traceability

A smart button is now available on invoices generating cash basis entries, so see them all at once. The move originally creating cash basis entries is also shown as a field on them.


// Commit 3
[IMP] account, sale, purchase, l10n_latam, l10n_ar: add the possibility to apply taxes after the invoice total, for withholding

It is now possible to check a boolean on the tax group, making its taxes appear below the 'Total' value on invoices, PO and SO. The tax will also be excluded from the taxed amount. This is intended for withholding taxes, which can now be implemented with negative taxes and a tax group with this field to True.

To do that, this commit entirely refactors the way amount_by_group worked, and replaces it with a more complete json field called tax_totals_json. It also streamlines the way taxe totals are displayed on invoices, PO and SO and makes it so that a common code is called instead of copy-pasting the same block 3 times as before.

[IMP] purchase: always display tax totals by groups on purchases orders

Before, tax totals on purchase.order's form were not shown by group, and were instead all aggregated in a single "Taxes" category. The same went for the pdf export. The portal view, though, did show the totals by group. We now display the tax groups in the same way all the time.

Task: 2457374

# Purpose

Allow an employee to manage more easily his appointments. He can now access his list of appointment types and creates
a new category of appointment types that let him create real time slot from his calendar. He can also give a link to an appointment type that use as time slots his availabilities between his work hours.

# Specifications

This commits introduces temporary and work hours appointment types.
The goal is to ease the scheduling of particular appointment type.

The first one represents temporary appointment type which contains
real time slots. This slots are created from the calendar view of the
calendar app for the actual user.

A work hours appointment type is an appointment type that is used to
propose a link to select a slot from the working hours of an employee.

This appointment category is managed by a new field:
appointment_type_category

* Calendar view:
	- Add a dropdown which display several options for the user
(creation of temporary appointment/slots and appointment types of the actual
employee).
	- Add a mode in the calendar view, to allow to create events as
before (default) and a mode to create custom slots for a custom appointment
type.
	- The end process of all the options allows to copy automatically the
link of the appointment type.

* Appointments Models:
	- Add one selection field in the calendar appointment type model:
appointment_type_category.
	- Add fields to the slot model to manage real time slots.

# Links
task-2287846
COM PR: odoo/odoo#69484
UPG PR: odoo/upgrade#2401