feature:added option to save a profile as detached(no inheritance)

[Azio-Pantheon]

Description

This gives users the ability to break the inheritance and have an independent user profile. It fixes #6323 and #4691. Works for machine/filament/process profiles.

Partially solves #1182, any profile name change in system profiles will cause user created profiles that are inheriting those system ones to fail to load. If you really hate system profile updates breaking your user profiles, you may now choose to save your user profiles as independent profiles. The obvious downside is, you now have to maintain your settings, and won't automatically get any updates from system profiles.(if you are already tinkering your own profiles, you probably don't want any changes to happen without your notice in the first place)

Screenshots/Recordings/Graphs

This option is only enabled under developer mode:

Tests

tested locally on windows 11

[Azio-Pantheon]

We might need to get the profile dependency feature merged before this. Otherwise, users may run into issues:
If you detach a machine profile from a system one, you will get no profile for filament and process to work with, because all of your filament and process are dependent on the system machine profile. With profile dependency tab enabled, you could find your user filament and process profiles under the system machine, then change the dependencies for them to only show up for your detached machine profile