New "react" project does not use latest AEM React Core Components (v2.0.1) and friends

### Expected Behaviour

When generating a project using:

```
mvn -B archetype:generate \
-D archetypeGroupId=com.adobe.aem \
-D archetypeArtifactId=aem-project-archetype \
-D archetypeVersion=37 \
-D appTitle="WKND SPA React" \
-D appId="wknd-spa-react" \
-D artifactId="aem-guides-wknd-spa.react" \
-D groupId="com.adobe.aem.guides.wkndspa.react" \
-D frontendModule="react" \
-D aemVersion="cloud"
```

The ui.frontend/src/package.json should automatically be set to use the latest AEM SPA-related npm modules - for example:

```
"@adobe/aem-react-editable-components": "^2.0.1",
"@adobe/aem-spa-component-mapping": "^1.1.1",
"@adobe/aem-spa-page-model-manager": "^1.4.4",
```
And any other updated dependencies required to use these (ex. Node build version, etc.) and any required updates to the sample code generated by the archetype to be compatible w/ the new versions of the modules.

### Actual Behavior

The actual behavior is the Adobe' npm dependencies are old (aem-react-editable-components is on 1.1.6 for example).

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

#### Steps to Reproduce

#### Platform and Version

#### Sample Code that illustrates the problem

#### Logs taken while reproducing problem

Start with the generated ui.frontend/src/package.json produced by the Maven archetype command in the issue, then inspect the generated sample code for compatibility with the requested AEM React module versions. Update the generated dependencies and any required Node or sample-code changes, and verify that a newly generated project uses the specified versions and builds successfully.

Written by the indexing model from the issue text.