Archetype 30/31 - Container 'Page Content' policy allowed components typo

### Expected Behaviour

Allowed components for "Page Content" policy correctly allows components.

### Actual Behaviour

Typo in policy causes form container to be missing.

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

#### Steps to Reproduce

Build from archetype 30/31 with Dynamic Media enabled.
```
mvn -B archetype:generate \
-D archetypeGroupId=com.adobe.aem \
-D archetypeArtifactId=aem-project-archetype \
-D archetypeVersion=31 \
-D groupId=com.test \
-D artifactId=test \
-D version=1.0.0-SNAPSHOT \
-D package=com.test.adobe \
-D appId=test \
-D appTitle=Test \
-D aemVersion=cloud \
-D sdkVersion=latest \
-D includeExamples=n \
-D includeErrorHandler=n \
-D frontendModule=general \
-D singleCountry=n \
-D includeDispatcherConfig=y \
-D includeCommerce=n \
-D includeForms=n \
-D sdkFormsVersion=latest \
-D datalayer=y \
-D amp=n \
-D enableDynamicMedia=y \
-D enableSSR=n
```

#### Platform and Version

Win or linux

#### Sample Code that illustrates the problem
```
# fgrep -A5 '
------------------------------------------------------------------------------------^
```

Problem lines in `master` branch :

https://github.com/adobe/aem-project-archetype/blob/522e0151b7919ce33de089a913857bac4a8cc3cd/src/main/archetype/ui.content/src/main/content/jcr_root/conf/__appId__/settings/wcm/policies/.content.xml#L287

https://github.com/adobe/aem-project-archetype/blob/522e0151b7919ce33de089a913857bac4a8cc3cd/src/main/archetype/ui.content/src/main/content/jcr_root/conf/__appId__/settings/wcm/policies/.content.xml#L291

https://github.com/adobe/aem-project-archetype/blob/522e0151b7919ce33de089a913857bac4a8cc3cd/src/main/archetype/ui.content/src/main/content/jcr_root/conf/__appId__/settings/wcm/policies/.content.xml#L293

Inspect src/main/archetype/ui.content/src/main/content/jcr_root/conf/__appId__/settings/wcm/policies/.content.xml at the linked lines 287, 291, and 293. Generate archetype 30/31 with Dynamic Media enabled using the supplied Maven command, then verify that the Page Content policy contains the correct form container path and the generated form container is available.

Written by the indexing model from the issue text.