In an AWS serverless application utilizing AWS Lambda functions with aliases, which deployment strategy allows for a new Lambda function version to be initially accessible to a specific percentage of production users, facilitating a controlled release process?
