KnotxServer response configuration

Should setting "allowedResponseHeaders" to wildcard result in all headers being allowed?
This approach works in "allowedRequestHeaders" section of HttpRepositoryConnector configuration.

Example:

`"knotx:io.knotx.KnotxServer": {
"options": {
"config": {
"allowedResponseHeaders": [
"*"
], ...
}
}
}`

Start at the KnotxServer configuration handling for allowedResponseHeaders and compare it with the existing allowedRequestHeaders wildcard behavior. Verify whether "*" permits all response headers, and add or update coverage so the intended wildcard behavior is demonstrated.

Written by the indexing model from the issue text.