feat: Web UI for auto-indexing #438

[mickol34]

Your checklist for this pull request

• I've read the contributing guideline.
• I've tested my changes by building and running mquery, and testing changed functionality (if applicable)
• I've added automated tests for my change (if applicable, optional)
• I've updated documentation to reflect my change (if applicable)

What is the current behaviour?
Currently there is no UI to provide data for auto-indexing.

What is the new behaviour?
This PR introduces web UI to API mentioned in #437.

Test plan

Check how everything is looking, if it responds properly, if there are any scenarios in which page should behave differently. Check if data is being parsed properly within endpoints, if there are any edge-cases regarding inputs. Any additional suggestions will be welcome.

Closing issues

fixes #438

[mickol34]

Currently these components operate solely on stub data, which should be later provided from endpoints in #437. For now it is possible to manually test page responsivity by manipulating these stub inputs. Any suggestions regarding visual side of this UI or additional features will be very welcome.

[mickol34]

Screencast.from.2025-02-11.10-22-52.webm

This video presents basic use cases for index page, including:

• going to dedicated indexing page from status page,
• usage of form inputs (textbox counting non-empty lines as individual inputs and two multiselects),
• sending requests to API (though currently they fail for obvious reasons),
• showing progress bar and clear queue buttons (progress percentage depends on allQueuedFilesLength and finishedQueuedFilesLength params, modified live at lines 49:50 in current version of IndexPage.js

[mickol34]

For some reason previous screencast got possessed by demons in the middle of form demo. This video should provide missing feedback.

Screencast.from.2025-02-11.10-32-39.webm