Feature Request: Pass arbitrary options to the build actions

**Description:**
Based on experience building `claudia pack`, the team learnt that people kept wanting to add certain tweaks (eg skip the .npmrc file, skip security audits, don’t create package.lock etc). NPM keeps adding these steps into their builds. So they introduced the ability to pass arbitrary flags to NPM.

**Pros**: Easy to support these one off cases
**Cons**: This breaks one of the tenets - "make this builder super easy to reason about". Arbitrary flags make the builder hard to reason about because the output one person gets on his machine will be different from output another person get, because of the flags they have configured.

Ideally, we should implement 80% of these requested features in the build action. But I am opening this feature request to collect use cases for passing arbitrary options to build actions.

**Request by build actions**:
1. node-npm

Commencez par lire la node-npm build action et les cas d’utilisation listés dans l’issue. Déterminez quelles options de build demandées devraient être prises en charge explicitement et comment les options arbitraires seraient configurées ; le travail est terminé lorsque le périmètre et le comportement acceptés sont définis, et que l’arbitrage entre commodité et reproductibilité est résolu.

Rédigé par le modèle d'indexation à partir du texte de l'issue.