chore: remove drag and drop to install extension workflow

[abose]

Reason for Removal

The drag-and-drop functionality for extension installation has been removed due to its limited usage and poor user experience. Previously, users had to navigate to the extension manager and drop a zip file into a specific area to install extensions, a process that was not very intuitive.
Removed the code as it was too much code doing too little ux things, and it was broken anyway.

Proposed Alternatives for Future

1. Adopting a method similar to VSCode, we will change the extension file type from .zip to .phx to indicate it's an extension for our editor.
2. Instead of requiring a specific drop location, users will be able to drag and drop the extension file anywhere within the editor. Doing so will initiate the extension installation process.
3. Additionally, double-clicking the extension file from the native file explorer/finder will launch the editor and start the extension installation workflow.

other changes

Tauri caches assets. so when we are developing an extension using load this project as extension workflow, upon a quick reload with the f5 key press without restarting the app, the stale cached extension code is served. So, now, we add a random prefix to the load path so that the cache is not hit on subsequent extension reloads for development.

Screenshot

before

after

[phoenixide]

Thank You for making this pull request.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.0% Duplication

[phoenixide]

Thank You for making this pull request.