Respect feature service edit settings for privileged accounts

[Zagorki]

Currently, when a feature service is published that has editing privileges (any combination of create, modify, delete) turned off, Portal admins (or users with the right role) can still edit through applyedits in REST or natively in Pro. This is true for hosted data and referenced from an enterprise gdb. Specifically for branch versioned data, we need to publish as the schema owner, so it really limits our ability to control editing rights. A Portal admin may not be the data administrator. I would like to see feature services adhere to the editing privileges that are set for all users. I am comfortable with publishing the data twice for viewing and editing needs and using groups to secure access.