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

Menu items for those features should be highlighted when browsing
associated pages for consistency in the Web UI.

When sidebar is in collpased mode, it was previously flashing from expanded
to collapsed when loading a page as its state was changed using javascript.

So prefer to use a cookie describing sidebar state that can be read server
side from django and injected in templates, this way the sidebar is ensured
to be in correct state in HTML code on page load.

eg. https://sentry.softwareheritage.org/share/issue/12730ae3258d4868a087863e7fe1c94a/
is '406 Not Acceptable'

The error output was filtered out due to the high amount of urllib3 debug
logs but those logs are now longer enabled.

So remove error output filtering to help debugging failed migrations.

It generates a lof of noise and clutters terminal a lot.

The target and root directory differ in this test, causing this assertion to fail
when the test actually runs

For staff users only, like other extrinsic metadata

which redirects to the 'proper' one based on extended SWHIDs.

It is more convenient for debugging than computing URL hashes;
and it will also be used in a template (which cannot really compute
SWHID, and would need non-trivial refactoring to get access to it)

It is purposefully discouraged to query the api-1-raw-extrinsic-metadata-swhid
endpoint directly, as extended SWHIDs should not be part of the public API.

Instead, clients should query api-1-origin first, and rely on the link
in its response to fetch metadata.

Prefer to use a div instead of an iframe to avoid blinking banner
on page load.

Nevertheless, keep the iframe view to ease embedding in external
WordPress website.

Replace use of django.conf.urls.url by django.urls.re_path.

Fix inbound_email appplication name.

Add a small hack to ensure django-js-reverse compatibility
with django 4.x (issue fixed upstream but not released).

Black reforms `word2vec.ipynb` otherwise (or complains the ipynb is not
installed)

It now allows setting custom strategies as 'target'

without either RFC5987/6266-encoding of the filename or RFC2231-encoding
of the header, gunicorn crashes when trying to decode the header as ASCII.

The banner will be displayed on archive.softwareheritage.org and
softwareheritage.org.

This imports the content of this PR to upstream:
https://github.com/untitaker/pytest-subtesthack/pull/7

Using older versions works for passing tests, but assertion failures
cause a very obscure traceback on teardown

For some reason it is not an issue within tox; but mypy has been
bugging me about this for a while.

Web API should be as dumb as possible and should not attempt to
lookup an origin with and without trailing slash in its URL.

rDWAPPS56fb869644ad45e0648f4ad45c07619d468019b4 introduced that
regression but that process should only be performed in a Web
UI context.

Related to D7980

djangorestframework-stubs 1.7.0 pin mypy to > 0.950 in its requirements,
thus the mypy pinning to 0.942 in tox.ini is no longer respected and
mypy 0.961 is used when running tox, leading to new typing errors.

So ensure mypy 0.942 is used until we bump mypy version used by swh.

rDWAPPSb54d930bed54cb0a87078952cfbb3bb621290eb3 turned the
from_query_string and to_query_string parameters mandatory
but they can be empty in that case (when a file is added in
a revision for instance).

Cypress use a default key press delay of 10ms which significantly
slow downs e2e tests when typing a long string in an input element.

So override the type command to remove that delay.

Locally, overall cypress tests execution is reduced by one minute
(from 6m36 to 5m37).

When rendering a markdown README coming from a github origin, use
showdown github flavor in order to enable HTML rendering options
specific to github (header id format for instance).

idx_storage.origin_intrinsic_metadata_get does not return the same
dict fields according to the swh-indexer version used.

As swh-indexer 2.0.0 is not yet deployed in production, we must ensure
backward compatibility with swh-indexer 1.x or the Web API endpoint
/origin/metadata-search/ will break.

It prevents possible issues in URL generation when providing a query parameter
that is not of string type.

See for instance bug fixed in rDWAPPS1c512a8365afb9485e9ac202046fd1ca4223a3c4
that could have been spotted by mypy if such rule was in place.

Because parameters of view functions for browse web application were
not typed, mypy was not processing the body of those functions and
thus typing errors could be missed.

So add typing to these function signatures and fix new mypy errors now
new code is processed.

Because parameters of Web API view functions were not typed, mypy was
not processing the body of those functions and thus typing errors could
be missed.

So add typing to these function signatures and fix new mypy errors now
new code is processed.

Promise was returned instead of the expected asynchronous result which
was causing issues when submitting save code now requests.

OriginIntrinsicMetadataRow API has changed: from_revision parameter
has been replaced by from_directory one.