`swa deploy` does not update `staticwebapp.config.json`

**Describe the bug**
When changing the `{appLocation}/staticwebapp.config.json` file and redeploying it (`swa deploy`) without rebuilding the application every time (e.g. for configuring routing or authentication) the configuration file inside the `{outputLocation}/staticwebapp.config.json` is not updated and thus subsequent changes are not applied to the static web app.

**To Reproduce**
Steps to reproduce the behavior:

1. Build an app
2. Type in command `swa deploy`
- Notice how the configured `{appLocation}/staticwebapp.config.json` is copied to `{outputLocation}/staticwebapp.config.json`.
4. Change the `{appLocation}/staticwebapp.config.json`
5. Type in command `swa deploy`
- The `{outputLocation}/staticwebapp.config.json` is not overriden but stays the same as before.

**Expected behavior**
`staticwebapp.config.json` in the dist folder should be overridden with the configured one before each deployment.

**Screenshots**
If applicable, add screenshots to help explain your problem.

```
{
"$schema": "https://aka.ms/azure/static-web-apps-cli/schema",
"configurations": {
"project": {
"appLocation": ".",
"outputLocation": "dist",
"appBuildCommand": "npm run build",
"run": "npm run dev",
"appDevserverUrl": "http://localhost:5173"
}
}
}
```

**Desktop (please complete the following information):**

- OS: Windows
- Version 11
- @azure/static-web-apps-cli: 2.0.1

**Additional context**
Add any other context about the problem here.
Just found it in the verbose output. If not file exists it seems to be copied, but otherwise this log output is missing:
```
Copying 'staticwebapp.config.json' to build output
```

**Workaround**
`rm {outputFolder}/staticwebapp.config.json && swa deploy`

Reproduce el problema con `swa deploy` cambiando `{appLocation}/staticwebapp.config.json` después de la compilación inicial y, a continuación, inspecciona la ruta de deployment que gestiona `{outputLocation}/staticwebapp.config.json`. Compara la salida detallada con el comportamiento de copia documentado. Se considera terminado cuando cada deployment refleja el archivo de configuración actual sin tener que eliminar manualmente la copia de salida.

Escrito por el modelo de indexación a partir del texto del issue.