Extension and semantic of "supported vob type" validation in trigger_helper.pm and acc.pm

Currently trigger_helper supports "clientvob", "adminvob" and "both". The wish is to extend the functionality to include "pvob", "adminvob", "UCMvob", "clientvob" and a extension to support custom vobtypes, eg. based on an attribute/label.

History
The trigger install information, which enables the trigger to be installed by simply excuting a script with "... -install -vob \thevob", also include information about which VOB types the specific trigger is intended for. Right now a trigger can be for either or both of adminvob and clientvob, but we need to extend the fuctionallity to also support UCM vobs and in future custom vob types (theorizing that we at some point need triggers designed for specific vobs og subtypes of vobs).

For the installation to work, the trigger need to define 2 variables ($TRIGGER_NAME and $TRIGGER_INSTALL), where the install string is both the trigger installation string (mktrtype ...) and the supported vob types.
"adminvob" and "clientvob" vobtypes is supported by the ACC functions "acc::is_adminvob" and "acc::is_clientvob", the vobtype "both" does no validation of vobtype, at all.
The functionality needs to be extended to support UCMvobs and pvob, logically by implementing new functions like "acc::is_UCMvob" and "acc::is_pvob" the the acc.pm.

A suggested future extension is to allow comma separated "supported vob" list and custom vobtypes based on an attribute/label on the vob.