[Bug]: Discrepancy between CLI and Documentation

### What happened?

The documentation says that if we use the command `dab init` and specify a config file that already exists, this config file will be overwritten with the new changes. However, currently the CLI command fails and shows a message that states that the user should delete the config file manually before using the command with that specific config file name.
https://learn.microsoft.com/en-us/azure/data-api-builder/command-line/dab-init?tabs=bash-cli#:~:text=If%20the%20target%20config%20file%20already%20exists%2C%20the%20command%20overwrites%20it.%20There%27s%20no%20merge.%20Use%20version%20control%20or%20backups%20if%20you%20need%20to%20preserve%20the%20previous%20file.

### Version

2.0.0-rc

### What database are you using?

Azure SQL

### What hosting model are you using?

Local (including CLI)

### Which API approach are you accessing DAB through?

_No response_

### Relevant log output

```Text
Information: Microsoft.DataApiBuilder 2.0.0
Information: Generating user provided config file with name: test-config.json
Error: Config file: C:\Users\rcernaserna\DAB\dab-testing-environment-bug-bashes\test-config.json already exists. Please provide a different name or remove the existing config file.
Error: Could not generate config file.
```

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Inizia dal punto di ingresso della CLI dab init e riproduci il comando con un file di configurazione di destinazione esistente, usando il comportamento documentato e l'errore della versione 2.0.0-rc come confronto. Il lavoro è completato quando il comando gestisce una configurazione esistente in modo coerente con la documentazione e il comportamento è coperto da un controllo di regressione appropriato.

Scritto dal modello di indicizzazione a partire dal testo della issue.