we use to have two entries for csv:

  - text/comma-separated-values
     - mimes: ["text/comma-separated-values"]
     - extensions: ["csv"]
     - globs: []
  - CSV document
     - mimes: ["text/csv", "text/x-comma-separated-values", "text/x-csv"]
     - extensions: []
     - globs: ["*.csv"]

but text/comma-separated-values does not really exist, rfc4180 recommends
text/csv.

The problem with this configuration is that when ERP5 picks a mime type
for csv extension, it uses text/comma-separated-values, as this one has
extensions set.

Change the configuration to delete "text/comma-separated-values" and keep
everything in "CSV document":

  - CSV document
     - mimes: ["text/csv", "text/x-comma-separated-values", "text/x-csv", "text/comma-separated-values"]
     - extensions: ["csv"]
     - globs: ["*.csv"]

Instead of disabling in javascript, which cause the button to be visible
for a few milliseconds, disable directly in the HTML file.

Do not hide "document properties", because it can be useful and it does
not hurt and "edit images" because we don't hide the buttons to edit
annotations either, so this is consistent.

The setter does this already so no change is expected, but these are API
misuses and they just look wrong.

Also, modernise syntax a bit.

See merge request nexedi/erp5!1855

it was removed during df2642cf (corporate_identity_test: update
snapshots for new cloudooo, 2023-11-29) because it looked unused, but it
was actually used.

   the update_catalog parameter is explicity destinated to the entries
   on the template_list, never to its dependencies resolved.

   The side effect was that reindexation is trigger to the whole list of
   business templates in the site.

These actions should be always displayed, not only when user can modify,
otherwise the action is no longer displayed once the transaction
becomes delivered.

also adjust test to use test name for expected image id

As utility to activate whenever we have a process going wrong and
we do not want disturb the user or stop (rollback) the process
but we do want developpers to be notified.

See merge request nexedi/erp5!1854

To follow the API as the new JSON editor

- It's not deprecated anymore.
- When activities are grouped at CMFActivity level, it specifies a number of
  activities that are generated at a time instead of a number of activity
  groups.
- The special None value means no limit.

In nexedi/erp5@39369169 the new option
'nofile' was added to set the soft limit of open file descriptors to its hard limit.
In nexedi/slapos!1451 (comment 193296) it was criticized that
the name of the option - 'nofile' - is too vague and in nexedi/slapos!1465 a new
name for the option was searched. Finally we agreed on the more explicit 'with-max-rlimit-nofile'.

See merge request nexedi/erp5!1843

  This gadget aims to edit json based on json schema.

See merge request nexedi/erp5!1853

since for column like 'delivery.start_date'
the field would be like 'listbox_delivery_start_date'

This was missing from f3435570 (ui_test: update
verifyImageMatchSnapshot screenshots for firefox 115, 2023-10-22)

See merge request nexedi/erp5!1840

See merge request nexedi/erp5!1835

See merge request !1841

See merge request nexedi/erp5!1831

See !1850

Pause to make sure the server has time to process the request.
This is of course not a good fix, but the future of this code is really
uncertain, so this should at least fix the failing test.

When account number method is set to account reference and the
transaction line has a node acquired from the invoice source or
destination organisation or person and when this node has a reference,
then this was displayed as an account reference.

We set a reference on Client 1 organisation to reproduce the problem.

Make it part of the caching method id so that changing the preference
immediately show new accounts.

This also moves the "user_name" argument that was an artificial parameter
not used only here to make the cache vary to the cache id, for
consistency and clarity.

This fixes dict formatting which was formatted like this with too long
values:

  {
    "a":
    "b"
  }

after we updated cloudooo.erp5.net with cloudooo!32

See merge request !1785

This method raises the same error as jwt's claim validator, as it was intended to be
called from the same exception handling block. So move it from "else" blocks into
the corresponding "try" block.