Duplicate string "lastpass.com" with `""` symbols located in default HTTPS allowlist entry

### Please answer the following questions for yourself before submitting an issue

- [x] Filters were updated before reproducing an issue
- [x] I checked the [knowledge base](https://adguard.com/kb/) and found no answer
- [x] I checked to make sure that this issue has not already been filed

### AdGuard version

4.13.2

### Environment

- OS version:Android 15 (originOS 5)
- Device:iQOO Z10 Turbo+

### HTTPS filtering

- [x] yes, I do

### Root access

- [ ] yes, I have it

### Integration with AdGuard VPN

- [ ] yes, I do

### Routing mode

Local VPN

### Ad Blocking

_No response_

### Privacy

_No response_

### Social

_No response_

### Annoyances

_No response_

### Security

_No response_

### Language-specific

_No response_

### Other

_No response_

### Which DNS server do you use?

Custom DNS

### DNS protocol

DNS-over-HTTPS

### Custom DNS

https://dns.alidns.com/dns-query

### What Stealth Mode options do you have enabled?

_No response_

### Issue Details

Steps to reproduce:
1. Open AdGuard for Android and go to Settings → General → Advanced → Export settings.
2. Extract the exported ZIP file and open `https_filtering_settings.json`.
3. Locate the `HttpsAllowList` array.
4. Find the entry for `lastpass.com`.

Actual result:
The entry is incorrectly formatted with escape characters: "\"lastpass.com\""

Expected result:
The entry should be formatted as a normal string: "lastpass.com"

### Expected Behavior

The default HTTPS allowlist entry for `lastpass.com` should be stored as `"lastpass.com"` without unnecessary escape characters.

### Actual Behavior

In the exported `https_filtering_settings.json`, the entry appears as `"\"lastpass.com\""`. While this may not cause functional issues, it is a formatting inconsistency that could confuse users or tools parsing the configuration.

### Screenshots

Screenshot 1

### Additional Information

This is not a user-added custom rule; it is part of AdGuard's default built-in allowlist. The issue exists in version 4.13.2 on Android.