feat: Upgrade React v18.3.1 and RJSF v5.24.2

[ferruhcihan]

Implements

https://jira.linode.com/browse/APL-514
https://rjsf-team.github.io/react-jsonschema-form/docs/migration-guides/v5.x%20upgrade%20guide
https://react.dev/blog/2022/03/08/react-18-upgrade-guide

Description

This PR upgrades React from v17 to v18, RJSF from v4 to v5, and also updates other related dependencies due to the React version upgrade, removes unnecessary files and dependencies.
Please check this => https://jira.linode.com/browse/APL-514?focusedId=555666&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-555666

Considerations

• I have tested the changes in both light and dark mode.
• I have considered the need for new unit tests.
• I have tested the changes on a cluster.
• I have included relevant documentation updates.
• I have an approved Figma design or have reflected my changes in Figma
• I have verified that the UI/UX is consistent in major browsers (e.g., Chrome, Firefox, Safari, Edge).
• I have tested the changes for responsiveness in different screen resolutions.
• I have tested expected error states and verified that the user is presented with informative error messages.
• I have tested the feature with unusual or extreme inputs (e.g., very long strings, empty states, clicking a button multiple times quickly).

[dennisvankekem]

regarding "I have tested expected error states and verified that the user is presented with informative error messages.". React router dom is throwing some errors in the console and definitely should be updated later to remove those errors in the logs. But for now it's not a blocker

[dennisvankekem]

LGTM, tested against all the considerations, only one question regarding ArrayField removal

[ElderMatt]

LGTM, I tested in multiple browsers. I tried looking into the types that were changed to any, but in a short time I was unable to fix it. It is something that can be looked at In the future.