Support disabling per-user advanced configurations

### Please agree to the following

- [X] I have searched [existing issues](https://github.com/cryptomator/cryptomator/issues?q=) for duplicates
- [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md)

### Summary

Add support for disabling the advanced configuration located in the user's home folder.

### Motivation

Per-user advanced configurations may pose a security risk through specialized malware.

### Considered Alternatives

_No response_

### Anything else?

The term "per-user advanced configuration" in the context of the Cryptomator desktop application is defined [here]( https://github.com/cryptomator/cryptomator/wiki/Advanced-Settings#setting-properties) and corresponds to the term "per-user configuration of a jpackaged application" as defined by [specification for the configuration of jpackaged apps.](https://bugs.openjdk.org/browse/JDK-8287060)

This issue depends on changes to the specification for the configuration of jpackaged apps.
Currently there is no upstream issue for this change; the [latest known update](https://bugs.openjdk.org/browse/JDK-8287060?focusedCommentId=14498086&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14498086) indicates that there are no plans to add such a feature.

Start by reviewing the linked Cryptomator Advanced Settings wiki entry and the JDK-8287060 specification issue to understand the per-user configuration model. Confirm whether upstream provides a supported way to disable it; the issue is done only when Cryptomator can enforce that restriction, but the payload notes no upstream plan for the required change.

Written by the indexing model from the issue text.