CUSTOM erp5_officejs_support_request: Add visa_file_reference as parameter and redirect to the expected view

In support request, we need to receive visa_file_reference and store it as causality. With this, we have the relation between Support Request and Visa File

Also, we change the action reference because the previous is not available in our scenario(Default View Action reference).

This will be used by Capago to assign a Support Request to Visa File

Requested in an email from Galien Renault with title "Retour livraison interface consulaire" document "Retour livraison Interface Consulaire ERP5 .pdf". Suppression des boutons d’action : “Sort” / “Edit” / “Select” , section 4.1.4, item a, page 14

Requested in an email from Galien Renault with title "Retour livraison interface consulaire" document "Retour livraison Interface Consulaire ERP5 .pdf" Suppression des boutons d’action : "Sort ", page 4.1.4 item A, page 14

> email from Galien Renault with title "Retour livraison interface consulaire" document "Retour livraison
> Interface Consulaire ERP5 .pdf" Suppression des boutons d’action : ““Edit” / “Select”, page 4.1.4 item a page 14

Requested in an email from Galien Renault with title "Retour livraison
interface consulaire" document "Retour livraison Interface Consulaire
ERP5.pdf", section 4.1.4d page 16

Requested in an email from Galien Renault with title "Retour
livraison interface consulaire" document "Retour livraison Interface
Consulaire ERP5.pdf", part 3.2.2c page 10

- Il devrait être impossible de crée"New Event" pour un
ticket au statut "Closed"

This action is not suppose to work, because they should a new post in the Suppport Request instead of a new event directly.

Because this breaks the sort and filter buttons in the new ERP5 UI

CUSTOM erp5_officejs_support_request_ui: Display causality reference(Visa File Reference) from Support Request

Requested in an email from Galien Renault with title 'Retour livraison interface consulaire' document 'Retour livraison Interface Consulaire ERP5.pdf' V1.0 2020-04-31 section 3.2.1 page 9 and 3.1.9d page 8.

- Rajouter la colonne "Visa Files Reference" en valeur par défaut de l liste 'Recent Update'
- La valeur du champ "Visa File Reference" doit etre la reference TESTVFXXX et non le nom du requester

In this custom support request app, document are sent as items in packing lists
and the default "Attach Document" action is confusing, because we have a
"Create New Document" action which creates the document as an item with its
initial implicit movement.

This script was returning organisations in random order !

When organisation does not have accounting periods, but another organisation at the same level of the same group has, the result was undefined.

This fixes by considering all organisation from the same group.

!6 rebased and in a big
commit so that we can start using that
SimulationTool: implement "linear" flow API

testInventoryAPI: silent pyflakes warnings

more interpolation implementation

inventory_list interpolation flow: support at_date & to_date

more and more interpolation API

interpolation

interpolation

group_by_time_sequence_list

testInventoryAPI: move inventory valuation methods in a dedicated test class

This should not be in test inventory list.

test: move Tracking API to a dedicated test module

inventory api: dirty way of disabling cache if keys such as node_category are used.

interpolation: security on SimulationTool_zGetInterpolationMethod

SimulationTool_zGetInterpolationMethod is called in restricted context
of Resource_zGetMovementHistoryList so it needs to be usable by
anonymous.

ZSQL Method does not read parameters from REQUEST, so it looks safe.

inventory_api: rely on catalog to add slot_index in the query

instead of implementing this logic in ZSQL's DTML

cf 2c54e0f5

because Domain.getRelativeUrl (and Category.getRelativeUrl) cannot be
restrictedTraverse'd

This reverts commit cfa272321aa8478583ed339b17913ab428d7207f.

When using checkPythonSourceCode integrated in the source code editor,
for a scenario where developer edit a component and save we can benefit
from caching the check message for the source code content, because the
same check that the one happening in the editor will happen when the
component is saved.

This cache varies on:
 - "component_packages" cache cookie which is reset every time some
component code is edited.
 - zope startup time to take into account editions of file system code.
This assumes that after reseting file system code zope will be
restarted.
 - portal_type, because the checks performed by this function also
depend on portal type.

this makes completions works when using Ctrl+space

This makes "Format Document" / "Format Selection" work.

because pylint is a bit slow on large components, debounce every 2
seconds. TODO: this is too slow.

For now this is just the portal_url, but I'm thinking it could be a
proper tool.

IIRC the only thing needed is that ERP5TypeTestCase.getPortal is an
ERP5Site

on very large python files (>1000 lines) sometimes they queue up and we
have to wait for all requests that were queued by zope.

XXX maybe this does not happen when accessing through haproxy/apache, I
am observing this when hitting zope directly

We make it possible to define function the same way it's currently
possible to define accounts. The idea is similar: to be able to use this
information in accounting generation rules.

The typical accounting generation configuration using this will use the
function defined on the supply line if any is defined and with a fallback
to the function defined on business process' trade model path.

For now we don't introduce such configuration by default, but this may
become part of  the configuration generated by configurator some day.

The view of accounting transactions have dynamic columns so that all the
information that matters the most is displayed directly on the "main"
view. This extends the columns to add a column for all the items attached
to accounting movements.

Without these accessors, we have to use constructs like:

    resource.edit(
        default_purchase_supply_line_destination_account='account_module/123'
    )

with the accessors, we can use:

    resource.edit(
        default_purchase_supply_line_destination_account_value=account,
    )

The former is a bit error prone, because typos in the property name
silently create a local propery and typos in the relative URL make a
"broken" relation.

odt_style comes with "Print" global actions which allows getting the
default form as ODT and convert it to selected format and DMS comes with
"Print" actions which return a PDF of the document content.

As a result, when user try to use Print, they have the same action twice
with no way to know which one is which.

This is detected by CodingStyleTestCase.test_DuplicateActions, but only
for configurations where both erp5_odt_style and erp5_dms are installed,
which is not the case in coding style test suite which only install the
miminmal dependent business templates.