[FEATURE]: Run Drizzle Studio Client Independently

### Describe what you want

First, let me say that drizzle is awesome and studio is beyond impressive!

I don't know if it's just me but accessing my db through 'local.drizzle.studio' (hosted by drizzle) makes me feel uncomfortable. I understand that the code purely runs on the 'client' side but if possible I rather run this locally for peace of mind. Is it possible maybe there's extra flag like --client or something that would also run the studio client? This way we can make sure the ports are not public. Again, I do understand the why it was done this way but for extra paranoid user, this would provide peace of mind when accessing the db. Thanks again and definitely a drizzle fan!

The issue names no files or tests. Start by locating how Drizzle Studio is launched through local.drizzle.studio and how its ports are exposed; define the independent client entry point and verify that the client can run locally without public ports.

Written by the indexing model from the issue text.