#704 Add ability to define a security manager for a package object, before any code of it runs for the first time

[Rony G. Flatscher]

The Rexx code used for creating Package objects seems to be run automatically at package creation time.

Currently it seems to not be possible to define a security manager with setSecurityManager method, before any of the package object's code runs which makes it impossible to supervise class constructors (any "::method init class" and in addition prolog code, unless in the latter case the package's code contains an "::options noprolog", which is not the case for most packages).

Because of this behaviour packages cannot be fully controlled from the beginning using a security manager like it is the case with methods and routines. (Methods and routines when created do not run their code at that point in time it seems, such that it is possible for them to set them to a security manager before running their code for the first time.)

Please add the ability to allow for supervising package objects with the help of a security manager right before any code of a package gets executed for the first time.