Is your feature request related to a problem? Please describe.
I’m unable to specify the Cloud SQL instance when deploying an agent with the adk deploy cloud_run command. Currently, there is no way to pass the --add-cloudsql-instances parameter like we do with the gcloud run services update command. This causes issues when trying to deploy an agent that uses session_service_uri with a Cloud SQL database.

Describe the solution you'd like
I would like the adk deploy cloud_run command to support an option for specifying the Cloud SQL instance (e.g., --add-cloudsql-instances), similar to the existing parameter in gcloud run services update. This would allow proper configuration of database connectivity during deployment.

Describe alternatives you've considered
I would like the adk deploy cloud_run command to support an option for specifying the Cloud SQL instance (e.g., --add-cloudsql-instances), similar to the existing parameter in gcloud run services update. This would allow proper configuration of database connectivity during deployment.

Additional context
Currently, the only workaround is to manually run gcloud run services update after deploying with ADK, to add the Cloud SQL instance. However, this adds extra manual steps and breaks the fully automated deployment flow.