Feat/auto browser and bad query fallback

[Kinfe123]

This change include

• first , idk if this is something to add but i feel it some of peeps might need it but personally i dont use it a lot which is authomatically opening of browser (default) when we spin up the backend rust server - since it is not allowing me to run mutliple port if 3030 is already in use.. i just hard coded the port which the browser opens
• second - i have added the error message fallback like the image below for those that returns a error from backend . but this can be to have a stack trace to be displayed instead of blindly letting them know that something went wrong like ,something beyond syntax highlighting.
  

[frectonz]

I like the automatically opening the URL thing, but i don't like the "No such resource returned ..." thing, i prefer the skeleton. If you remove the that i will merge this PR.

[Kinfe123]

do you think skeleton would make sense for the users who aint know whether their query fails or not.. or we can stop the loading skeleon if the query fails to do so.

[frectonz]

Ok yeah, we should do this

• show the loading skeleton, in the loading state
• show nothing, in the error state

Since i want people to directly type in their queries and have the data fetched automatically, i don't want them to be bombarded with a "No such resource error".

[Kinfe123]

yeah we can handle that by debouncing but yeah it is better to return a nothing.

[frectonz]

Yeah but don't add debouncing. I want querying to feel extremely fast, deboucing will just add a delay. Since people are running the server on their own local machine, we don't care about how many times they hit the /query route. Debouncing would have made sense if we were calling an external API.

[Kinfe123]

hmmm....makes sense , it is fixed by now