The keys in the `count_by_state` dict in SupportRequest_getSupportRequestStatisticsAsJson.py
was hardcoded in previous version. This commit can add the keys to the dict dynamically according
to the states of Support Request. Thus the code can still work if there has new state added to
Support Request.

Users may upload PDF files when they submit comment under a support request.
This commit allow user to view the PDF file after they upload it.

The 'form_view_discussable' allow user to visit the 'OfficeJS View' in classic ERP5 interface.
This was copied from 'form_view' and the 'discussable' part is not implemented in this page template.

In the case the CTP is for a refund

First commit of monitoring renderjs application in erp5.
Monitoring is a render js application which uses jio to sync slapos instance promises result and display on web browser.

/reviewed-on !347

only change ids of gadget (reference and content already changed)

make all graph gadget names like gadget_field_graph_plotly.html/js . We should not have any more "officejs" or "erp5" in name, since theses gadgets could be used for any kind of application.

A Form is rendered by assuming the REQUEST is clean and first set 'here' as
the context. Then there may be listboxes with rely on 'here' and set 'cell'
temporarily. At last, for easier configuration of listbox fields, 'cell' has
precedence over 'here' when rendering (in particular since
commit 4fa84233).

Based on this, the only sane solution is to
- clean up the REQUEST (remove 'here' and 'cell')
- render the FormBox in the new context (which sets 'here'): inside a ListBox,
  the context is the cell
- restore 'here' and 'cell' as they were

Which allows FormBox/ListBox inside FormBox/ListBox, recursively
(but obviously no ListBox inside ListBox).

The previous code didn't work in the following case:
- a Order Line and Packing List Line having an identical tab
- the left pane for Order Line information
- the other for Packing List Line information
  (-> empty when there's no related PL)
- a listbox (with subobjects of the PL line)
Which is implemented as follows:
- a Form for the left pane
- a Form for the Packing List Line, with a FormBox
  (to display Order information) and a ListBox
- the Form for the Order Line only has a FormBox, that uses 1 of the 2 other
  Forms depending on the presence of a PL (if there's one, it's rendered in the
  context of the PL)
-> FormBox(FormBox, ListBox)

As you can see, FormBox is used here to factorize forms. Without this patch:
- the outter FormBox crashed on `del REQUEST.other['cell']`
- the inner FormBox was rendered with a wrong 'cell'

Another change is to pass the field & REQUEST to the context method.

/reviewed-on nexedi/erp5!346