The Discuss app has been visually softened to reduce harsh contrast, especially in dark mode. This makes conversations easier on the eyes with gentler colors, lighter separators, fewer borders, and more comfortable sidebar spacing.

Especially in dark theme, UI had too much contrast, which makes using Discuss more exhausting than it should.

PR makes the following improvements to make Discuss look more pleasing:

- Dark theme: selected item is greyish rather than greenish
- Discuss app borders and composer have half reduced opacity
- Dark theme: background of conversation is slightly less dark
- Message bubbles no longer have borders
- White theme: date separator is slightly less visible
- Discuss sidebar channel items have more vertical spacing

Before (white)
![before-white](https://github.com/user-attachments/assets/b873898b-0489-4e97-ba5e-dd0388738500)
After (white)
![Screenshot 2024-11-19 at 14 38 43](https://github.com/user-attachments/assets/ee433321-ec5b-48b4-9051-a289fc4ff67c)

Before (dark)
![before-dark](https://github.com/user-attachments/assets/8038b49e-603e-410a-a56b-ac998169b6f0)
After (dark)
![Screenshot 2024-11-19 at 14 38 31](https://github.com/user-attachments/assets/9cbecadf-88c6-4f28-a250-9e84e6c34760)

The point of sale IoT box image is being updated to a newer Raspberry Pi operating system release. This should prevent startup hangs related to display initialization and fix a log rotation configuration issue that could stop a service from starting.

Backport of #187206.

For the next IoT box image, we will upgrade to the latest version of RPi OS Lite. This fixes an issue on bootup where the display is not initalised (hangs waiting on `dev-dri-card0/start`).

Also removes the `wtmp` and `btmp` paths from `logrotate.conf`. These paths were duplicated from existing logrotate config files, causing the service to fail to start.

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

Adds documentation guidance for the GSTIN status feature in the India localization settings. This helps users understand where to find official information and how the feature supports GST compliance workflows.

task-4143187

Related PR
- https://github.com/odoo/documentation/pull/11324

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

The editor’s insert option now uses the clearer name “Media” instead of “Image,” matching the media selection dialog and better reflecting that it can handle more than images. Users can still find it by searching for image or icon, while video insertion remains available through the media dialog where enabled.

This commit:
- renames the Image command to Media to better reflect its broader functionality and match the dialog's title ("Select a media").
- adds search keywords so that both "image" and "icon" are aliases to the Media command, improving discoverability.
- removed the Video command as it is currently not used in html_field (it is still available as a tab in the media dialog when the "disableVideo" option is set to false, effectively merging the Video command into the Media command).

task-4264248

Orders paid with the on-site payment option are now confirmed automatically instead of remaining pending. This ensures related delivery or collection steps are created promptly, reducing manual follow-up and improving the customer experience.

As on_site payment provider is a custom one, transaction is created as pending. Therefore, SO is not confirmed and picking is not created which
 is not convenient for the customer.

task-4267776

This update marks the mail mailbox route as read-only, helping the system handle mailbox-related requests more efficiently. It is a behind-the-scenes improvement that can reduce unnecessary database overhead without changing the user experience.

The code upgrade command is now easier to automate, with cleaner output, clearer required options, and better handling of progress and dirty files. This helps developers and release teams run upgrade preparation more safely and predictably.

Moved the logs/progress on stderr so it is possible to silent them using
a shell redirection `2>/dev/null`. Simplified what is written on stdout
so it is scriptable.

Moved `sys.stdout.isatty()` outside of `print_progress` so the function
is evaluated once, and not everytime we print a progress. Should speedup
the scripts a bit on runbot.

Moved the `print_progress` in scripts inside the loop, so it doesn't try
to `print_progress(..., 0)` and crash on a division by 0. The runner now
takes care of logging 0% and 100%, along with the script name.

Changed `-t/--test` for `--dry-run`, for consistency with other posix
commands such as rsync.

Made so it exits 1 when there are dirty files.

Added a `--script` option to run a single script. Useful in development
when we want to test a single script and not run all the scripts of a
given version.

Removed the default of `--from`, we couldn't agree on a sensitive
default value. `--from` (or `--script`) is now required.

Used mature `parse_version` from the tools, which is suitable to parse
odoo versions.

Added a long text that describes what "code upgrade" is. It is used as
the module docstring and the --help description.

Used cross-plateform \r instead of unix specific \033.

Skipped `__pycache__` folders, not strickly necessary as `.pyc` files
would nevertheless be skipped via `AVAILABLE_EXT`.

Replaced some string manipulation on paths by pathlib.

Subscription billing now better coordinates invoice creation and payment processing to reduce conflicting updates during automated runs. This helps high-volume systems process recurring invoices and payments more reliably, with fewer interruptions from database conflicts.

Before this commit, amount_to_invoice was computed in the cron when the
invoice was created as it depends on qty_invoiced. Unfortunately, the
compute would be triggered and the ORM would try to write on the
sale.order record at the same time than the cron would continue his job.
it would end up with concurrent updates.

This commit ensure that the compute method is inhibited during the cron and is triggered at the end of it.

task 4216148

Attendance Gantt and list views now hide archived employees by default. This keeps workforce planning screens focused on current staff and reduces clutter for managers reviewing attendance schedules.

With this commit, by default, The gantt view and list view don't dispayed archived employees.

task-4208052

Salary configurator dropdowns such as company car, company bike, and spouse income can no longer be cleared to an empty value. This helps ensure compensation configurations remain complete and avoids missing information during salary package setup.

Problem
----------
Dropdown fields in the salary configurator (like company car, company bike or spouse income) can be set to null with the red cross

Objective
----------
Set these fields non-nullable : remove the cross

Solution
----------
Add the "is_required" field for benefits like in personal infos. Remove the not hidden condition for the personal info drop down.

task-4188242