This is required to run cypress tests in parallel.

CYPRESS_PROJECT_ID environment variable could be used but better
add project id in config.

Some tests were flaky in this test suite due to missing wait instructions
ensuring save code now requests datatable got fully rendered.

When running cypress tests in parallel, each runner must have its dedicated
webapp database. Using the same database cause issues as multiple cypress
processes modify its content concurrently and make some tests fail due
to unexpected database state.

It is needed to run cypress tests in parallel using sorry-cypress.

Related to T4398

It enables to modify another code coverage output directory when running
cypress tests in parallel and thus avoid race conditions when multiple
cypress processes try to write to the same coverage output file.

It enables to modify the code coverage output directory when running
cypress tests in parallel and thus avoid race conditions when multiple
cypress processes try to write to the same coverage result file.

It only depends on swh.web.browse which is a base django application
always activated so it can be moved into its own django application.

Display info about the number of add forge now requests (filtered or not)
below the table on the left.

Set default ordering to descending submission date.

It heavily depends on browse templates so better moving it here.

Also changes view URL from /embed/<swhid>/ to /browse/embed/<swhid>/
but keeps backward compatibility by adding a redirection from the
old URL to the new one.

Related to T4398

It makes it easier to find related endpoints than alphabetically
sorting URLs.

This removes datatables enhancements on this page, as they are longer
relevant for a split table.

Fix "cannot import name 'ADD_FORGE_MODERATOR_PERMISSION' from
'swh.web.auth.utils'" when autodoc processes the admin_views
module from swh.web.add_forge_now.

This is such a better naming.

Related to T4398

Related to T4398

Related to T4398

Related to T4398

Related to T4398

Centralize all templates, views and urls related to add forge now into
the add_forge_now django application.

Related to T4398

Move all templates, views, urls and commands related to the save code now
feature into its dedicated django application.

Also introduce a new django command rename_app to easily rename a django
application when developing or deploying.

Previously the save code now models were located in the swh.web.common
application that will be removed so that is why that application renaming
to swh.web.save_code_now is mandatory to avoid errors when running migrations.

Related to T4398

Move all templates, views, urls and commands related to the mailmap
feature into its dedicated django application.

Please note that the initial migration will not perform any database
operations as the tables have already been created by the swh.web.auth
django application the mailmap feature was previously located at.

Related to T4398

Towards reorganizing swh-web features into multiple django applications,
introduce the following changes regarding their settings:

- Declare a fixed set of base django apps and enable to add extra ones
  through configuration

- Add application templates directory to django templates search paths

- Automatically register URLs of selected django applications

- Inject swh-web django app names in templates to check a feature is enabled

Related to T4398

Inject transitions dict into Django template instead and pass it to js.

This will prevent submission of add forge now requests with invalid
forge URLs from the Web UI and the Web API.

Previously, the last moderator and modification date for an Add Forge Now
request were retrieved by the model serializer.

While it is enough for display, it prevents to sort the requests by last
modification date when using datatables.

So prefer to add the last_moderator and last_modified_date to the Request
model instead and update their values when a new RequestHistory model
is created.

When running migrations, existing requests stored in production database
will have the values of these new fields set according to their history.

It enables to help debugging swh-web JavaScript errors in Sentry Web UI
by demangling transpiled, minified and bundled JavaScript in order to
view source code context obtained from stack traces in its original,
untransformed form.

It looks weird when email clients soft-wrap on smaller number
of columns; eg. Thunderbird defaults to 72 when editing in
plain text.

The ctags indexer has been stopped a long time ago and recently got dropped from the
indexer base code. As the api exposing this in the webapp is hidden, we can safely
remove them.

This also fixes build [1].

Related to T4273

[1] https://jenkins.softwareheritage.org/view/swh%20master%20(draft)/job/DWAPPS/job/tests/3265/console