Define dependencies in a separate file

[m-aciek]

We plan to have a second entrypoint script. Let's migrate from inline dependencies definition to a separate file.

[StanFromIreland]

What benefit does it have over a simple requirements.txt for the dashboard?

[m-aciek]

It follows the latest best practices. Though we'd need to start tracking version of dashboard, as minimal pyproject.toml would need to be as follow:

[project]
name = "pydocs-translations-dashboard"
version = "1"
dependencies = [
     "gitpython",
     "potodo",
     "jinja2",
     "docutils",
 ]

So I'm a bit torn, I've updated the ticket title and description not to decide yet.

[StanFromIreland]

It would have to be a bit longer.

The proposed throws:

Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error
  
  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [14 lines of output]
      error: Multiple top-level modules discovered in a flat-layout: ['generate', 'repositories', 'completion', 'visitors', 'contribute', 'build_status', 'translators'].
      
      To avoid accidental inclusion of unwanted files or directories,
      setuptools will not proceed with this build.
      
      If you are trying to create a single distribution with multiple modules
      on purpose, you should not rely on automatic discovery.
      Instead, consider the following options:
      
      1. set up custom discovery (`find` directive with `include` or `exclude`)
      2. use a `src-layout`
      3. explicitly set `py_modules` or `packages` with a list of names
      
      To find more information, look for "package discovery" on setuptools docs.
      [end of output]