Webapp template description does not match with files generated

Nobody has claimed this yet.

When the `webapp` template is used, the `backend` directory is not generated.

Running:

```bash
harness-application webapp-example -t webapp
```

Generates the following files tree:

```
webapp-example
├── api
│   ├── config.json
│   └── openapi.yaml
├── backend
│   └── webapp_example
│   └── __main__.py
├── deploy
│   └── values.yaml
├── Dockerfile
├── frontend
│   ├── build.yaml
│   ├── package.json
│   ├── package-lock.json
│   ├── README.md
│   ├── src
│   │   ├── App.tsx
│   │   ├── assets
│   │   │   └── icon.png
│   │   ├── components
│   │   │   └── RestTest.tsx
│   │   ├── index.ejs
│   │   ├── index.tsx
│   │   ├── rest
│   │   │   ├── api.ts
│   │   │   ├── base.ts
│   │   │   ├── common.ts
│   │   │   ├── configuration.ts
│   │   │   ├── git_push.sh
│   │   │   └── index.ts
│   │   ├── styles
│   │   │   └── style.less
│   │   └── utils
│   │   └── history.js
│   ├── tsconfig.json
│   ├── webpack.config.dev.js
│   └── webpack.config.js
├── README.md
└── test
├── api
│   └── test_st.py
└── e2e
└── landing.spec.ts
```

We can see that the `backend` folder only contains a directory with a `__main__.py` file in it.

However `harness-application --help` mentions that:
```
- webapp (webapp including backend and frontend).
```

Start with the webapp template and the output of `harness-application --help`, then reproduce `harness-application webapp-example -t webapp` to compare the description with the generated tree. Determine whether the template or its help text is authoritative, update the mismatched behavior or description, and verify the generated structure and help output agree.

Written by the indexing model from the issue text.