erp5_officejs_support_request_ui_test: Add test to make sure we have all expected actions to access support request web site

* Check if each portal_type has the expected view action
* add test to cover all possible attachments in a Support Request

erp5_officejs_support_request_ui: Simplify code to render the expected action to preview any attachement document

Hard coding to select action_object_view we will never use web site configuration.

If we always get links from action_object_view, Support Request will always break if we change View Action Category on web site.

Having a big "Generate RSS" button on the front page is strange, because the front page button are for common use cases that users are supposed to execute a lot.

For example, makes sense to have a "Submit new Support Request" button, because users are using this app to submit support requests, but generating RSS is very exceptional action, so we wanted to remove it from the front page.

Also, we changed:
- change the generate_rss_link action in Support Request Module, to directly call SupportRequestModule_generateRSSLinkUrl.py instead of the form.
- change SupportRequestModule_generateRSSLinkUrl to display the form at the end.
- Use Base_renderForm like for erp5_crm
- Put the RSS url in the REQUEST
- change the gadget field configuration to use the value from the REQUEST (if not found, put None)
- change the gadget implementation to display the URL in an html5 string field  + a button

See merge request !1227

Without it, it is not possible to upgrade instances since:
nexedi/erp5@48c45fbd

[test/upgradeOldDataFS] use UI callables
Ensure the admin will able to trigger the upgrader

erp5_corporate_identity_test: test pdfs are only used to store data then check converted image, so one pdf is enough

- test updated

Do not limit by default

Querying the catalog does not limit the result by default..
See nexedi/erp5@241a87a1

what's wrong with this anyway

See merge request nexedi/erp5!1226

When a request got retried after a conflict error, a:

    TypeError: getPublisherDeadlineValue() takes exactly 1 argument (0 given)

was raised.

Instead of adding a new test to cover this, run all tests from
ZPublisher module (except a few which had suspicious errors).

This actual error happened when running
ZPublisher.tests.testPublish.testPublisher before the fix.

See merge request nexedi/erp5!1220

Install more business templates such as erp5_web or erp5_dms, to confirm that we can also update these business templates.

Run the tests with "full indexing", to be more realistic and to be sure that we don't hide problem that would happen when reindexing action definitions or property sheets.

See merge request nexedi/erp5!1228

See nexedi/erp5@981f2e61

In a real ERP5 actions, roles etc are all indexed, so it's more
realistic to simulate update with full indexing.

We are using html2canvas to render the page in a canvas element, but
because the canvas element was created in the selenium runner frame (and
not the tested frame), if some extra css fonts were loaded in the custom
page they did not apply.

To make the snapshot use proper fonts, we create the canvas in the
tested page.

Selenium asynchronicity does not use Promise, but calls function while
it returns true, we were implementing this logic in two places and
implementing wrongly because some case of errors where not reported.

Introduce a wrapper that makes turns Promise into a function returning a
boolean like selenium is using and use it in setFile and
verifyImageMatchSnapshot commands

Also a bit more of jsdoc comments for typescript.

This can help debugging test failures on test nodes

ERP5: Remove Capacity/GLPK: never used and broken since glpk Python module is not in ERP5 Software Release neither.