Add credentials profile in aws_lambda config (#33293)

Signed-off-by: Juan Manuel Ollé <jolle@mulesoft.com>

Mirrored from https://github.com/envoyproxy/envoy @ d41761887ee34c8d015e2fd8272d118d14912081

envoy/extensions/filters/http/aws_lambda/v3/aws_lambda.proto

@@ -17,6 +17,7 @@ option (udpa.annotations.file_status).package_version_status = ACTIVE;
 // [#extension: envoy.filters.http.aws_lambda]
 
 // AWS Lambda filter config
+// [#next-free-field: 6]
 message Config {
   option (udpa.annotations.versioning).previous_message_type =
       "envoy.config.filter.http.aws_lambda.v2alpha.Config";
@@ -55,6 +56,12 @@ message Config {
   // Changing the value of the host header can result in a different route to be selected
   // if an HTTP filter after AWS lambda re-evaluates the route (clears route cache).
   string host_rewrite = 4;
+
+  // Specifies the credentials profile to be used from the AWS credentials file.
+  // This parameter is optional. If set, it will override the value set in the AWS_PROFILE env variable and
+  // the provider chain is limited to the AWS credentials file Provider.
+  // Other providers are ignored
+  string credentials_profile = 5;
 }
 
 // Per-route configuration for AWS Lambda. This can be useful when invoking a different Lambda function or a different