Also ensure apt-transport-https package is installed.

Current debian stable (bullseye) does not package postgresql-autodoc
so remove it from packages list and add alternative install instructions.

yarnpkg debian package does not play well with nodejs installed from
nodesource so add instructions to install its latest version through
its homemade debian package.

- Use the generic `virtual environment` instead of `virtualenv` and
  point to the official Python documentation.
- Use the internal reference to the getting started doc.
- Mention there is tons of good tips in the documentation about
  the Docker environment.
- Update the link to the documentation on how to submit patches.

The `--now` flag to `systemctl disable` will stop (on top of disabling)
the given services. `systemctl disable` also accepts multiple services
as argument.

We can thus replace 4 commands in the developer setup documentation by a
single one.

The tutorial on how to “run your own Software Heritage” felt quite dry.
Meanwhile, more details on how to start using the local
instance were already available in the documentation on how to use
the Docker environment.

So we pull in the relevant sections from
`swh-environment/docker/README.rst` to complement the existing tutorial.

Related to T3117

Related to T3117

Related to T4135

Related to T4373

It can be convenient to run the global swh documentation in the
current venv instead of using tox (notably to save time by skipping
dependencies installation).

It looks like the Makefile in docs folder was not really maintained
regarding that kind of documentation build so fix it in order to
restore local build.

This would warrant a more thorough guide, but I'm not the best person to
write such a guide, and this is better than having nothing.

Sphinx started to crash recently because of that not needed file
processed by apidoc.

Related to T4324

To explicit how to use the generated credentials.

Related to T4259

It got displayed again after reintegration of custom CSS rules but
it should have been removed since a while.

Add landing page of listersrs high-level documentation displaying
available ones in a table with the following column:

  - logo and name of the lister linking to its specific documentation

  - related links: source code, developer doc, development activity

  - current status: production, staging or development

  - link to related grant if any

Create one rst file per lister to further document.

Related to T3117

Add landing page of loaders high-level documentation displaying
available ones in a table with the following column:

  - logo and name of the loader linking to its specific documentation

  - related links: source code, developer doc, development activity

  - current status: production, staging or development

  - link to related grant if any

Create one rst file per loader to further document.

Related to T3117

Encountered issues have been fixed so we can remove the pinning of sphinx.

It is a common practice to open an external link in a new browser
tab so process external links with javascript when a documentation
page got loaded to enforce such behavior.

Corresponding RST document has been renamed to uri-scheme-swhids.rst
so add a redirection for URL backward compatibility.

With recent enough versions of setuptools/setuptools-scm, the pip
dependency resolver is now capable of sorting out our full dependency
tree. We can just install all packages at once (which does the
dependency resolution step once).

To speed up the process even more, inline the few "build" (setup.py)
dependencies to allow disabling build isolation (which creates a new
venv and installs setuptools-scm in it for every single package).

That hook can be frustrating as it can discard a long commit message
if it finds a typo in it so better removing it.