file not found in build context or excluded by .dockerignore: stat package.json: file does not exist

> Please provide us with the following information:
> ---------------------------------------------------------------

### This issue is for a: (mark with an `x`)
```
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behaviour that used to work and stopped in a new release)
```

### Minimal steps to reproduce

Container images are stored inside container registries. You can easily create a container registry and upload an image of your app to it in a single workflow using Visual Studio Code.


See it here: [Tutorial: Deploy to Azure Container Apps using Visual Studio Code](https://docs.microsoft.com/en-us/azure/container-apps/deploy-visual-studio-code#create-the-container-registry-and-docker-image)

### Any log messages given by the failure

```bash
Step 4/10 : COPY ["package.json", "package-lock.json*", "npm-shrinkwrap.json*", "./"]
COPY failed: file not found in build context or excluded by .dockerignore: stat package.json: file does not exist
2022/06/05 20:24:24 Container failed during run: build. No retries remaining.
failed to run step ID: build: exit status 1
```

### Expected/desired behavior
Create the container registry and Docker image.

Once the registry is created and the image is built successfully, you are ready to create the container app to host the published image.

### OS and Version?

Linux debian 5.17.0-1-amd64 #1 SMP PREEMPT Debian 5.17.3-1 (2022-04-18) x86_64 GNU/Linux

### Versions

- code - version: 1.67.2
- Docker (extension) - version: 1.22.2
- Azure Container Apps (extension) - version: 0.1.1

### Mention any other details that might be useful

> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.

Commencez par le tutoriel Azure Container Apps indiqué et examinez le contexte de build, .dockerignore, package.json, package-lock.json et npm-shrinkwrap.json référencés par l’étape COPY en échec. Reproduisez le build documenté de l’image conteneur et déterminez pourquoi package.json n’est pas disponible ; c’est terminé lorsque le registre et le build de l’image Docker réussissent.

Rédigé par le modèle d'indexation à partir du texte de l'issue.