[Bug]: nextcloudcmd does not sync hidden files

### ⚠️ Before submitting, please verify the following: ⚠️

- [x] This is a **bug**, not a question or a configuration issue.
- [ ] This issue is **not** already reported on Github (I've searched it).
- [ ] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)

### Bug description

Files having a name starting with a dot are not synchronised by `nextcloudcmd`, although option `“-h”` is given on the command line.

Note that initially I had to check the boxes “not already reported” and “up-to-date version” above although this is not true. I provide reasons for this below.

### Steps to reproduce

1. Set up a Nextcloud instance
2. Do the initial sychronisation on the client side with
```bash
nextcloudcmd --non-interactive -h --user USER --password PASSWORD \
/local/path https://server.example.org
```
3. Add a dotted (hidden) file to `/local/path`, e.g. `.test`.
4. Do the synchronisation of (2) again.

### Expected behavior

The file `.test` appears on the server side, e.g. at `nextcloud/data/USER/files/.test`.

### Which files are affected by this bug

n/a

### Operating system

Linux

### Which version of the operating system you are running.

Debian 12

### Package

Other

### Nextcloud Server version

30.0.13

### Nextcloud Desktop Client version

3.16

### Is this bug present after an update or on a fresh install?

Fresh desktop client install

### Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

### Are you using an external user-backend?

- [ ] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other

### Additional info

- This is re-issuing https://github.com/nextcloud/desktop/issues/100, which could not be re-opened.
- I cannot use client >3.16 because it is not included in the Linux distros I use, and I was unable to compile it myself.
- I cannot use a newer Nextcloud server version because I was unable to make them work with nextcloudcmd.
- For the server, I use the Nextcloud image on Docker Hub.