Minor frontend fixes

[maximi4321]

Summary

This PR includes small changes that were pending to be implemented in the frontend.

Type of change

• Bug fix.
• Refactoring.

Changes

1. Fixed the responsiveness in ResultsPage.jsx. The drawer no longer covers the table even if the screen width is changed.
2. The browser's autofill functionality has been disabled for text input fields, because React has some problems handling autofill on controlled components
3. A bug in the table for selecting runs to execute has been fixed (RunnerDialog.jsx). Now the user's selection is preserved (previously, all runs were reselected on any update).
4. The modals for confirming the deletion of an item in the tables have been refactored. Since they were all very similar to each other, they have been replaced with a generic component.
5. The API for editing datasets has been restored, which previously was not working due to compatibility issues with the backend.

How to Test

1. Go to DashAI/DashAI/front and run yarn build
2. Go back to DashAI/ and run python -c "import DashAI;DashAI.run()"
3. Follow the steps in the "Screenshots" section.

Screenshots

Click to toggle the screenshots

1. Responsiveness in results page.

2. Browser autofill is disabled

3. Keeps the users run selection

Select.webm

4. Generic modal to delete item

5. Restored edit dataset API

edit.dataset.webm

[pbadillatorrealba]

The changes in general are fine!
I left some comments and questions.

[pbadillatorrealba]

Question: Is the margin left assigned from the left edge of the image? I think it would be better if it was with respect to the drawer.

[maximi4321]

Yes, the margin left is assing from the edge.

I am trying to define the margin with respect to the drawer, and I think I managed to do it. But by modifying that, now i haven't been able to make the table take up the entire space.

[pbadillatorrealba]

I think that Drawer is not the best component to use in this case (it is more intended to be the drawer where the navigation menu of the page is located) but List.

This will allow you to have the objects live in the same view and therefore, the size calculations are done with respect to the list and the table.

Suggestion: You could implement a view with two Grid, the one on the right with a small size where the List of experiments (ListItems) goes and the one on the left where the visualization goes.
And then make the grid sizes variable according to the size of the page using the typical sm, md, lg, etc...

[pbadillatorrealba]

It looks good!

I think Container (in app.jsx) is the component that is causing the strange behaviors regarding the view responsive sizes.
For now, it's fine, but in the future we will have to think about how to deactivate it.

A minor margin change was requested.

Question: Could you disable the black background of the experiment list?