Reactify configuration editing without changing stored setting formats

[Montekkundan]

Brief summary of changes

• Rewrites the main Configuration module page from the Smarty/jQuery form into a React entrypoint.
• Adds JSON endpoints for loading configuration categories/settings and saving setting updates.

Testing instructions (if applicable)

• Open /configuration/ as a user with the config permission and confirm the page loads as the React UI without the old Smarty form.
• Click through the category tabs and confirm settings load for each category.
• Edit a text/email/textarea setting and confirm the value saves on blur and persists after category reload.
• Edit a boolean setting that currently stores true/false, then one that stores 1/0, and confirm each keeps its existing storage format after saving.
• Add and remove values from a multi-value setting such as scan types or instruments and confirm the updated values persist.

Link(s) to related issue(s)

• Resolves [Configuration] module rewrite with react #5213
• Related to Create user UI not showing mandatory fields. #5218

[MaximeBICMTL]

Although they are currently (unfortunately) pervasively used in LORIS, propTypes and defaultProps are removed in the next version of React. I am a strong advocate that we should use Typescript exclusively for all new Javascript code moving forward. To be discussed at a next meeting.

https://react.dev/blog/2024/04/25/react-19-upgrade-guide#removed-proptypes-and-defaultprops

[skarya22]

Can you add the changes from #8471 to .eslintrc.json and Makefile?