Inconsistent path formation when using swaConfigLocation

**swaConfigLocation** doesn't seem to be building the path to the configuration file properly. I have placed both SWA and SWA CLI configuration files on the folder `my-folder`, and run
`swa deploy --config my-folder/swa-cli.config.json`
_swa-cli.config.json_ has a `deploy` section with the property `swaConfigLocation`.

If I set `"swaConfigLocation": "."` or `"swaConfigLocation": "./"` then I get the error `ENOENT: no such file or directory` because it tries to find the file at `\staticwebapp.config.json` instead of `\my-folder\staticwebapp.config.json`. That is, it is using the parent folder instead of `my-folder`. **This was not the case in earlier versions of SWA CLI**.

If I set `"swaConfigLocation": "my-folder"` or `"swaConfigLocation": "./my-folder"` then I get an `ENOENT: no such file or directory` error because it tries to find the file at `\my-folder\my-folder`. On this occasion, swaConfigLocation is appended to `my-folder` instead of the parent folder (as opposed to what happens in the previous example).

If I set `"swaConfigLocation": "staticwebapp.config.json"` or `"swaConfigLocation": "./staticwebapp.config.json"`, then the path seems right `\my-folder\staticwebapp.config.json`, but I get an `ENOTDIR: not a directory` error, because it is expecting a folder rather than a file.

So there seem to be an inconsistency regarding the use of the parent vs `my-folder` directory. I am using **Windows 11** and **Azure Static Web Apps CLI 2.0.8**. In earlier versions of SWA CLI I always used `"swaConfigLocation": "."` and never had this problem.
Could you please provide some advise?