Botpress Cloud - AWS Lambda integration is missing the `secretAccessKey` field

[hgmarquezp]

Description:
When configuring the AWS Lambda integration in Botpress Cloud, only the accessKeyId and region fields are shown. The secretAccessKey field is missing, causing all Lambda requests to fail with a signature error:
The request signature we calculated does not match the signature you provided.

Steps to reproduce:

1. Go to Integrations > AWS Lambda
2. Click "Install"
3. Only accessKeyId and region are requested

Expected result:
All three fields (accessKeyId, secretAccessKey, region) should be shown as stated in the documentation.

Impact:
Unable to use AWS Lambda integration in production.

Tested in multiple browsers and with new bots. Issue persists.