I'm working on a project that I plan to deploy to railway that would be really complicated for the end user if it was processing user information while a new instance is deployed and the old one is removed. What I was hoping for was to be able to do some sort of Blue-Green Deployment, where I can direct any new requests to the new deployment while the old one finishes up whatever it needs to, but it doesn't seem theirs a way to do this exactly. I did find RAILWAY_DEPLOYMENT_DRAINING_SECONDS that I think I should be able to configure to a very large amount but then can I somehow indicate to railway that it is ready to be removed? Or does it only do it after the RAILWAY_DEPLOYMENT_DRAINING_SECONDS time?