Terminal Package Generates Unnecessary 403 Requests When User Lacks Required Policy

[markusguenther]

Issue Description:

Overview:
The Shel.Neos.Terminal package in Neos currently generates a 403 Forbidden error in the backend when a user lacks the necessary policy. Given that the Terminal button is hidden in such cases, it seems redundant and counterintuitive for the package to trigger this error.

Expected Behavior:
Ideally, when a user does not have the required policy for the Terminal, the package should prevent the generation of a 403 Forbidden request, especially considering that the Terminal button is already hidden in such scenarios.

Steps to Reproduce:

1. Create a user without the required policy for the Terminal (e.g. Editor).
2. Log in to the Neos backend.
3. Observe the network requests, where a 403 Forbidden request is generated by the Shel.Neos.Terminal package.

Actual Result:
The Shel.Neos.Terminal package triggers a 403 Forbidden request even though the Terminal button is appropriately hidden when the user lacks the required policy.

Expected Result:
The package should suppress the generation of a 403 Forbidden request when the user does not have the necessary policy, given that the Terminal button is hidden in such cases.

Additional Information:

Neos version: 7.3
Terminal package version: 1.1

[Sebobo]

The terminal only shows up when the request succeeds. Do you have a better idea on how to find out from a plugin whether something is allowed?

[markusguenther]

Could resolve one part of the issue, but did not know before that the request is used to know if someone has permissions.
Need to think about it :D

[markusguenther]

I am not sure if you like it, but I now have a new command that has permissions for everybody to check if the user has available commands and that returns true or false.

With that approach we save the errors in the console but have one extra request.