AWS Libraries are excluded when deploying to Adobe I/O Runtime, causing initialization errors

there is a change in behaviour in helix-deploy since version 9.3.11 (most likely due to [this](https://github.com/adobe/helix-deploy/pull/602) PR). now, IO RT actions that are importing packages like helix-google-support are failing with initialisation error (Initialization has failed due to: Error: Cannot find module '@aws-sdk/client-s3).

### Expected Behaviour

### Actual Behaviour

### Reproduce Scenario (including but not limited to)

#### Steps to Reproduce

#### Platform and Version

#### Sample Code that illustrates the problem

#### Logs taken while reproducing problem

Start by reviewing the behavior change in helix-deploy PR 602 and tracing how deployment packaging handles AWS libraries for Adobe I/O Runtime. Reproduce the failure with an action importing helix-google-support or @aws-sdk/client-s3; done means the deployed action initializes successfully with those imports available.

Written by the indexing model from the issue text.