[Feature] Ideas and Suggestions for User Interfaces

### Search before asking

- [X] I had searched in the [issues](https://github.com/labring/laf/issues?q=is%3Aissue) and found no similar issues.

### Feature Request

While the Laf positioning is for non-coders to be able to use, I still suggest that the interface of Laf can evolve towards the direction of VSCode.

Currently, the entire interface resembles a backend system, which is not very user-friendly and lacks aesthetics.

* Avoid using rounded corners.
* Reduce the spacing between sections to make the interface more compact and increase the visible area for code editing.
* Incorporate MonacoEditor in more places, such as the log viewing interface.
* Use a console interface similar to Chrome's console, which provides a more user-friendly output for console.log logs.
* Use MonacoEditor with line numbers in the interface for API testing and database management, making it easier to view and edit.
* It is not recommended to use the cmd+r shortcut as it may conflict with the browser's refresh shortcut.
* The code editing area currently uses overflow: hidden, which prevents MonacoEditor tooltips from being displayed. It is advisable to reconsider the layout approach.
* Consider adding the ability to switch between tabs for functions.
* Use more navigation components instead of divs, as this allows for opening new tabs with the right-click function.

I am willing to contribute the aforementioned suggestions. May I ask if it's possible to develop and debug Laf.dev by connecting to it locally without deploying k8s to the cloud?

### Are you willing to submit PR?

- [X] Yes I am willing to submit a PR!

No files, tests, or specific entry points are named. First review the current UI areas for code editing, logs, API testing, database management, and function tabs, then narrow the suggestions into one agreed change with a clear completion condition.

Written by the indexing model from the issue text.