Add more configuration options (inputs and variables) for Dependency Scanning v2 CI template

Release notes

Problem to solve

During dogfooding of the v2 CI template for Dependency Scanning, we've observed situations where the provided inputs where not sufficient to configure the feature.

This leads to have to override the CI job which is something we'd like to avoid, and use either CI variables or preferably inputs to customize the behavior.

Proposal

Consider adding inputs to configure the following:

1. artifacts_expire_in
2. needs
3. rules
4. before_script/after_script

⚠️ Before deciding to add a new input we should consider the feasability and the implication for long term maintenance and various usages of the CI template (e.g. security policies)

Intended users

Feature Usage Metrics

Does this feature require an audit event?