Fix: Fixed an issue where it wasn't possible to edit some file permissions

[0x5bfa]

Description

Fix an issue which has been reported.

Motivation and Context

I've been aware of that there're a lot of lack of function. As a part of improving, I fix an issue where some security functionalities are missing.

Validation

• If you have a file with no ACEs
  • Remove all ACEs
  • Open its properties and see Security again
  • You can see a message that is telling there's no ACE
• If you have a file whose owner is not current user
  • Change owner to whatever that is not you like SYSTEM, Administrators
  • Open its properties and see Security again
  • You can see a message that is telling you do not have Read Permission access rights and to see ACEs, change owner.

Removal & Its Rationale

• Removal of functionalities
  • I removed a functionality of changing access control type
  • I removed a functionality of changing access control flags
  • I removed a functionality of changing inheritance flags
  • I removed a functionality of converting inherited ACE to explicit one
  • I removed a functionality of removing inherited ACE
• Rationale of that removal
  • I will add back them in a further PR. Those functionalities are not at work long time before and so I decided those are might as well not to be.
• Removal of this message
• Rationale
  • File Explorer can see ACEs with admin privileges even if the current user doesn't have Read Permission. However, WinUI3 app cannot elevate current instance without no restarting, so there's no meaning that Continue button exists. In this case, in Files, Files suggest that you should take ownership of the object even if the current user can see ACEs with admin privileges like File Explorer do when even admin privilege doesn't work (for example, the owner is SYSTEM or something else that doesn't belong to Admin group).
    

PR Checklist

• Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
  • Related Feature: Add function to change ACE's inheritance in SecurityAdvanced page #11551
  • Related Feature: Add function to change access controls in SecurityAdvanced page #11550
  • Related Feature: Add function to change ACE type in SecurityAdvanced page #11549
  • Related Feature: Integrate Advanced Security page into properties window #11930
  • Closes Bug: Cannot add/remove access control entry #12255
  • Related Code Quality: Refactored code for security settings #11471
• Did you build the app and test your changes?
• Did you check for accessibility? You can use Accessibility Insights for this.
• Did you remove any strings from the en-us resource file?
  • Did you search the solution to see if the string is still being used?
• Did you implement any design changes to an existing feature?
  • Was this change approved?
• Are there any other steps that were used to validate these changes?
  • See Validation section.

Screenshots

Before (File Explorer or previous Files)	After

[yaira2]

@0x5bfa can you link the issue for these changes?

[0x5bfa]

Done.

[0x5bfa]

@QuaintMako Could you review?

[QuaintMako]

@QuaintMako Could you review?

I should be able in the upcoming days, probably around Sunday at worst.

[QuaintMako]

Also, I did not test any fonctionnality, I'm not versed at all in the security processes.

[yaira2]

LGTM