feat: Modify the console page graph display(enhancement)

[shubihu]

Modify the console page to run the ngql query statement. If there is a graph, the graph will be displayed by default, as well as the background color of the graph. In addition, the displayed full-screen icon has been moved to the header of the outbox.

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number: #312

Description:

Originally, the table was displayed by default, the graph background was a little gray, and making the full-screen icon difficult to spot.

How do you solve it?

Modify the console page to run the ngql query statement. If there is a graph, the graph will be displayed by default, as well as the background color(#F9FCFF) of the graph. In addition, the displayed full-screen icon has been moved to the header of the outbox.

Special notes for your reviewer, ex. impact of this fix, design document, etc:

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

wangjiabin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[yyh0808]

You have done a great job of thinking! Thank you very much for your suggestions.

Here, I would like to explain the reason for the design. I still suggest placing the enlarged window in the bottom right corner because according to the original plan, we also have a function to expand the window that needs to be placed in the same position.

Regarding the idea of changing the order of tables and graphs, after many discussions, at least some people want to directly see the code execution results instead of visualization because developers' primary work is business development.

So for now, we don't plan on merging your code. However, you made excellent suggestions and I received your desire for customization. We will discuss ways to provide more flexible layouts for these features to meet different developers' habits.