[Feature] Provide convenient scripts and package for Venice services (controller, router, server)

Nobody has claimed this yet.

### Willingness to contribute

I can collaborate

### Feature Request Proposal

Users need a way to bootstrap conveniently the services, configure them.

Currently it is pretty hard to bootstrap the services:
- no default configuration files
- no scripts to start/stop the services
- no way to configure logging/JVM properties
- no released tar.gz package
- no easy way to run the admin tool

### Motivation

> #### What is the use case for this feature?

Bootstrap the services in a VM.
Provide support for a future standard docker image

### Details

Some examples:
- ZooKeeper: https://github.com/apache/zookeeper/tree/master/bin
- Pulsar: https://github.com/apache/pulsar/tree/master/bin

### What component(s) does this bug affect?

- [X] `Controller`: This is the control-plane for Venice. Used to create/update/query stores and their metadata.
- [X] `Router`: This is the stateless query-routing layer for serving read requests.
- [X] `Server`: This is the component that persists all the store data.
- [ ] `VenicePushJob`: This is the component that pushes derived data from Hadoop to Venice backend.
- [ ] `Thin Client`: This is a stateless client users use to query Venice Router for reading store data.
- [ ] `Fast Client`: This is a stateful client users use to query Venice Server for reading store data.
- [ ] `Da Vinci Client`: This is an embedded, stateful client that materializes store data locally.
- [ ] `Samza`: This is the library users use to make nearline updates to store data.
- [X] `Admin Tool`: This is the stand-alone client used for ad-hoc operations on Venice.

Start by mapping the Controller, Router, Server, and Admin Tool entry points and comparing the bin directories in the referenced ZooKeeper and Pulsar projects. Identify how configuration, logging, JVM properties, service lifecycle, packaging, and admin-tool execution are currently handled. Done means the services can be bootstrapped and configured conveniently, with a released tar.gz package and a clear path toward Docker support.

Written by the indexing model from the issue text.