#3808 Fix single binary config Pull request opened by Yicheng-Lu-llll Describe your changes The existing flyte_local.yaml configuration file has fallen out of date, causing issues when running single binaries. The standard process ideally looks like this:

# Start a k3s cluster, create pods for postgres, minio.
flytectl demo start --dev
# Start all backends (flyteidl, flyteadmin, flyteplugins, flytepropeller) and HTTP Server in a single binary 
sudo make compile
flyte start --config flyte_local.yaml

This PR introduces necessary updates to the flyte_local.yaml configuration file. Checks

flytectl demo start --dev
# 👨‍💻 Flyte is ready! Flyte UI is available at <http://localhost:30080/console> 🚀 🚀 🎉 
# ❇️ Run the following command to export demo environment variables for accessing flytectl
#         export FLYTECTL_CONFIG=/root/.flyte/config-sandbox.yaml 
# 🐋 Flyte sandbox ships with a Docker registry. Tag and push custom workflow images to localhost:30000
# 📂 The Minio API is hosted on localhost:30002. Use <http://localhost:30080/minio/login> for Minio console

sudo make compile
flyte start --config flyte_local.yaml

# running a hello_world sample from flytesnacks
pyflyte run --remote core/flyte_basics/hello_world.py my_wf
# Go to <http://localhost:30080/console/projects/flytesnacks/domains/development/executions/f40d94cefb5e74fe6b09> to see execution in the console.

pyflyte run --remote core/flyte_basics/deck.py wf
# Go to <http://localhost:30080/console/projects/flytesnacks/domains/development/executions/f39a9c56828e54bb09be> to see execution in the console.

Able to run the task Able to see the deck: Able to see the kubernetes logs: flyteorg/flyte ✅ All checks have passed 6/6 successful checks