[Bug]: 3.16.3 Crashes with "realloc(): invalid next size" on first start (before configuration)

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

- [x] This is a **bug**, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I've searched it).
- [x] 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

With Version 3.16.3-20250418.133140.a3b9b08db-1.0~noble1 installed from https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client the app crashes on first start (when normally the configurations dialog should appear, asking for the server address). When starting on command line, the error message ""realloc(): invalid next size" appears and whoopsie asks to send a report.
When nexcloud-client is already configured, there is no issue, just works fine. I have one user configured with 3.16.2 installed, no problems for that user after update.

### Steps to reproduce

1. fresh install Version 3.16.3-20250418.133140.a3b9b08db-1.0~noble1 installed from https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client or update to that version. I used sudo apt install nextcloud-client-caja
2. start Nextcloud for the 1. time (e.g. create a new user and start the nextcloud client)
3. configuration dialogue will not open, but nextcloud client will crash

### Expected behavior

Configuration dialogue should open and ask for the address of the Nextcloud Server.

### Which files are affected by this bug

nextcloud-desktop, nextcloud-client-caja

### Operating system

Linux

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

Ubuntu Server 24.04 with Mate Desktop

### Package

Distro package manager

### Nextcloud Server version

not aplicable, as there is no connection to server at the time of the crash

### Nextcloud Desktop Client version

3.16.3

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

Fresh desktop client install or update from 3.16.2 to 3.16.3, if the nextcloud client is started for the first time with 3.16.3 with no configuration present for the respective user

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

Encryption is Enabled

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

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

### Nextcloud Server logs

```shell

```

### Additional info

I cannot provide Desktop Client Logs, because Desktop Client do not even open for the first time.

Workaround: Downgrade, e.g. using
`sudo apt-get install nextcloud-desktop=3.11.0-1.1build4 caja-nextcloud=3.11.0-1.1build4 `
then start Nextcloud for the first time, configure it for this user, after successful configuration, you can update again to 3.16.3 using
`sudo apt update && sudo apt upgrade`