Add permission/access control for launching of Wayland applications

[conniefry]

As a pxscene product owner, I want to be able to control what pxApps can launch particular Wayland applications in my pxscene environment.

Currently, we have a configuration file for Wayland apps that maps an app 'name' to the app location on disk. However, we need to have a way to control access so that only permitted/trusted pxApps can launch any or specific Wayland apps when they know the name of the app(s).

• Design permissions/access mechanism
• Code is implemented with > 80% code coverage
• Test cases are defined
• Tests are run and passing

Internal Reference: XRE2-1128

[bobseamon]

pxscene security model documentation has been expanded to include an application section.
(@conniefry to supply github link once moved from private location; see Internal Reference info.)

In the permission section, "applications" determine what a pxApp can launch when using scene.create({t:'wayland', cmd:"browser"})

• If an application name appears in the allowed section ("browser" in this case), it can be launched.
• If an application name is not contained in the application section, or if the application is listed in the blocked section, it cannot be launched.
• If an application uses the application manager API, then permissions for that application should include allowed:["*"], otherwise applications will not be able to be launched from application manager.

Test cases should include both positive and negative testing based on the above scenario.