feat: improve translations editing

[perierc]

What

This PR changes a few things about the edit entry page:

• The children and parents are now listed horizontally instead of vertically, to make the information more compact
• If there are no parents or no children, we display "No parents" instead of "Parents" "None"
• The translations edition section has been revamped, using Tagify. Translations can be added freely via a blank entry, and tags can be deleted or reordered with drag&drop.
• The backend has been updated to make the ID of the node change when the first translation of the main language changes. If the new ID already exists, it sends back an error to the frontend and the changes are not saved in the database.
• When the first translation of a language changes, an alert informs the user on the frontend that the display name of this language (and ID of the node if it is the main language) will change if changes are saved.
• Fixed an issue in the backend where the tags were normalised whereas they shouldn't.
• The modified files that were still in Javascript (jsx) have been transformed to Typescript (tsx) and typed.

This PR also includes a lot of refactoring to simplify the code and avoid unnecessary rerenders.

Video demo

new-node-edition.mp4

ID change (first translation of the main language changes) :

id-change.mp4

Part of

#323

[eric-nguyen-cs]

Good PR, does what it is supposed to do!
However, I left quite a bit of comments concerning the previous code's quality
Not sure if it should be handled in this PR or not... (But my stance on that is to refactor at the same time of adding new features, or better yet to do a refactor PR before the feat changes)

[alexgarel]

I see @eric-nguyen-cs did a good review, I didn't take the time to understand tsx files much, sorry.

[alexgarel]

@eric-nguyen-cs I let you validate it if @perierc thinks it's ready.

[eric-nguyen-cs]

You can merge after solving the important comments