does &ZOWEUSER still need SUPERUSER.FILESYS ?

[OnnoVdT]

Customer content

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

When ZWESECUR was created, a permit to SUPERUSER.FILESYS was added to allow Zowe Server to write data to the install directories (zlux-app-server/deploy), regardless of the permission bits assigned to these directories.
Now that install directories are read-only I think we can remove this permit.

Describe the solution you'd like
A clear and concise description of what you want to happen.

If the Zowe started task still needs to write data during runtime, the target location must be defined during configuration, and appropriate permits must be assigned at that point. There is no more need to be able to ignore permission bits.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Leave as-is.

Additional context
Add any other context or screenshots about the feature request here.

The less permits Zowe Server has, the less chance there is that a bug can be exploited.

---

Engineering team info (eg https://github.com/zowe/explorer-jes/issues/4)

As a [type of user],
I want [some goal]
so that [some reason].

Details/notes
[Detail - implementation notes]

Acceptance Criteria

*Scenario 1: [Title]
Given [context]
And [some more context]...
When [event]
Then [outcome]
 And [another outcome]...

[Joe-Winchester]

Sounds good - for 1.9 let's take it out and test it given everything is 755