PEAK XOOPS - Privileges about altsys

conventional myblocksadmin and mytplsadmin checks the privileges 'system_admin' from system module.

- myblocksadmin XOOPS_SYSTEM_BLOCK (System Admin rights -> Blocks)
- mytplssadmin XOOPS_SYSTEM_TPLSET (System Admin rights -> Templates)

But this harms independencies among each modules.
Because 'system module' will be just a normal module can be exchanged, in the near future of XoopsCube.
And the privilege's constant like XOOPS_SYSTEM_* is defined only system module.

'system module' is not a part of CORE of XOOPS.
(At least, it is an important fact with XoopsCube)

Thus, I've changed privileges of altsys from conventional myblocksadmin/mytplsadmin.

altsys does not check 'system_admin' at all, but 'module_admin' of altsys itself.
If you want to controll privileges of altsys library, check/uncheck of altsys's module_admin.

An exception:
mypreferences inside altsys checks module_admin of the targeted module.
It sounds natural, does not it?