WIP: Feat: new tree view

[MarceloRobert]

Changes

• Adds a new table with the direct TreeListing data, without the need for processing
• Adds a new view to consume that data
• WIP: alter ingester to insert the data into that table

How to test

• Run the migrations for the new table
• Start the ingester
  • Create a temporary folder for the submissions as backend/kernelCI_app/management/commands/tmp_submissions (you can change the path, just update the command below)
  • Make sure you have your trees-name.yml file somewhere. It usually is on /backend/volume_data as a result of the treeproof command. If you are feeling lazy and you don't want to run the command, there's an example file here (Google Drive link)
  • Make sure you have a couple of example submission files for testing. You can grab some in this zip file here (Google Drive link)
  • Export the environment variables in your terminal, pointing one of the databases to the local one. Make sure the local one is set as the default one with USE_DASHBOARD_DB=True
  • Now you'll be able to run the command with poetry run python3 ./manage.py monitor_submissions --spool-dir kernelCI_app/management/commands/tmp_submissions --trees-file volume_data/trees-name.yaml (being in the /backend directory, update the paths if necessary)
• Insert submissions in the folder and check that they are being inserted in the database
  You can also test the ingester on docker, make sure the environment variables are on .env.backend and use docker compose run --rm backend before running the command shown above.

Closes #1558

[WilsonNet]

shouldn't be more 1:1 to the frontend? like, only one commit tag instead of an array

[MarceloRobert]

I'm basing off of the treeView response, which returns the tags as an array (btw a list[list[str]] which I think is a mistake), and the frontend is the one to only select the first one I think