Invalid dispatcher configuration - including not existing files

### Expected Behaviour
Dispatcher config can be used for fresh project.
### Actual Behaviour
Trying to run dispatcher with clean dispatcher config is failing.

### Reproduce Scenario (including but not limited to)
#### Steps to Reproduce
1. Create project

```
mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
-D archetypeGroupId=com.adobe.aem \
-D archetypeArtifactId=aem-project-archetype \
-D archetypeVersion=39\
-D aemVersion=6.5.9\
-D includeErrorHandler=y\
-D appTitle="AEM project" \
-D appId="aem-project" \
-D groupId="com.aem.project"
```

2. Run dispatcher with adobe docker image. I am using `adobe/aem-ethos/dispatcher-publish:2.0.121` which is prepared for cloud but hopefully I can reuse it with on prem as well. Use project dispatcher configuration with the dispatcher running.

Dispatcher fails to start with error

```
httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 35 of /etc/httpd/conf.d/dispatcher_vhost.conf: Syntax error on line 62 of /etc/httpd/conf.d/enabled_vhosts/aem-project_publish.vhost: Include/IncludeOptional: No matches for the wildcard '*.proxy' in '/etc/httpd/conf.d/proxy', failing
```
3. Dispatcher should start.

Seems that this code is the problem

```

SSLProxyEngine on
Include /etc/httpd/conf.d/proxy/*.proxy

```

Generating project using options shown above does not generate any proxy configuration.

#### Platform and Version
Mac OS

#### Sample Code that illustrates the problem

#### Logs taken while reproducing problem

Reproduce the clean project with the Maven archetype command, then inspect the generated aem-project_publish.vhost and the referenced dispatcher_vhost.conf and httpd.conf paths. Check how /etc/httpd/conf.d/proxy/*.proxy is included when no proxy files exist. Done means the dispatcher starts successfully with the generated configuration.

Written by the indexing model from the issue text.