[FEAT] Moved driver pages from Ember

[eva-vashkevich]

Summary

Fixes #9274

Moved Drivers page from Ember to Vue 3.

Occurred changes and/or fixed issues

Moved Cluster and Node drivers page to Vue 3. Now, Steve is used to list drivers, but Norman is used to modify and create. No other areas should be affected.

Technical notes summary

Areas or cases that should be tested

1. Cluster management -> Drivers:

• [ ] Cluster drivers should be displayed
• [ ] If you go to Node Drivers tab, node drivers should be displayed
• [ ] You should be able to Refresh Kubernetes metadata (cluster drivers only)
• [ ] You should be able to create new driver (both)
• [ ] You should be able to edit existing active drivers (both)
• [ ] You should be able to deactivate and activate existing active drivers (both)
• [ ] You should be able to delete existing drivers (both) - node driver has to be deactivated first
• [ ] Correct menu items should be shown for each driver (both) - should be all for cluster drivers, varies for node drivers

2. Cluster manager -> New cluster provisioning:

• [ ] Driver list should reflect currently installed drivers

Areas which could experience regressions

Provisioning can experience regression since it uses driver information to show available providers.

Screenshot/Video

Checklist

• [X] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• [X] The PR has a Milestone
• [x] The PR template has been filled out
• [X] The PR has been self reviewed
• [X] The PR has a reviewer assigned
• [x] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• [x] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes