ccweb-add-on-scripts start command cloud provide custom HTTP header config param?

### Expected Behaviour
ccweb-add-on-scripts start command cloud config `Cross-Origin-Embedder-Policy` header or custom HTTP header, because I'm need test app for enabled COEP, only cloud modify `inversify.config` for it, cloud provide some config param for that?

### Actual Behaviour
ccweb-add-on-scripts start can't add custom HTTP header

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

#### Steps to Reproduce
not need

#### Platform and Version
@adobe/ccweb-add-on-scripts/1.0.0 darwin-arm64 node-v18.17.0

#### Sample Code that illustrates the problem
not need

#### Logs taken while reproducing problem
not need

Start by tracing the ccweb-add-on-scripts start command and the cloud configuration mentioned in the issue, then inspect inversify.config to find where HTTP behavior is configured. Confirm how the development server handles headers; done means the start command accepts a configuration for Cross-Origin-Embedder-Policy and other custom HTTP headers.

Written by the indexing model from the issue text.