refactor(backend,taxonomy-editor-frontend): Handle background task on frontend

[Piv94165]

Current situation

• If parsing takes too long, the frontend times out, resulting in a timeout notification :

• Only successfully parsed taxonomies are displayed in the existing projects list. Failed or loading taxonomies are not visible.

To be done

• Project Creation Page: Users should land on a loading page upon creating a project, prompting them to refresh the page for updates
• Projects Listing: Ensure all projects are visible in the table, including those that failed or are still loading
• ¨Project Status: Display project statuses (successfully parsed, parsing failed, parsing in progress) in the projects list

These enhancements will offer a more comprehensive view of project statuses, provide clarity to users during parsing, and ensure visibility of all projects in the list, even if parsing fails or takes longer than expected.

Screenshot

A small text reminds user to reload the page to see taxonomy

In the list, the project status is displayed.
Not only the open projects are listed but also the other ones.

Part of

(https://github.com/orgs/openfoodfacts/projects/103/views/1?pane=issue&itemId=46878339)

[Piv94165]

Link: #304 (comment) needs to be merged prior to this PR for correct functionality.

Remarks:
During the import of a taxonomy, the task runs in the background. However, the backend is unable to send any response due to the synchronous nature of the following functions:

self.create_nodes(filename, multi_label)
self.create_child_link(multi_label)
self.create_previous_link(multi_label)
self.create_fulltext_index(taxonomy_name, branch_name)
self.create_parsing_errors_node(taxonomy_name, branch_name)

This results in the page loading indefinitely if the user tries to access existing projects while a new project is being created, as the backend cannot respond to the frontend until parsing is complete.

The synchronicity of these functions appears to be causing the backend's inability to respond to the frontend. Converting them to asynchronous operations might be necessary to resolve this issue.

[alexgarel]

Cool. Small improvement proposed.

[alexgarel]

Maybe you could set project status FAILED only if create_project did not fail ? (create project could return created project and you could test it here, remember to create the variable with None before the try though to be sure it exists.

[alexgarel]

Thank @Piv94165 !

There are still a bit of things to improve.

[alexgarel]

Maybe, in another PR I think we will have to provide a way to filter by status !

[alexgarel]

@Piv94165 should we close this PR ? If I remember well you merged those changes in another PR right ?