Support filtering document types resulting from a template query

When on a folder, a cms user can add a new document. via FolderWorkflow or via the Channel Mngr DocumentTemplateQueryService the user gets the list of possibly document types that can be added. This is done for example via the query node (hippostd:templatequery) stored at 'new-document'

/hippo:configuration/hippo:queries/hippo:templates/new-document

containing

//element(*,hipposysedit:namespacefolder)/element(*,mix:referenceable)/element(*,hipposysedit:templatetype)/hipposysedit:prototypes/element(hipposysedit:prototype,hippo:document)

Or for example

/hippo:configuration/hippo:queries/hippo:templates/new-blog-document

containing

//element(*,hipposysedit:namespacefolder)/element(*,mix:referenceable)/element(*,hipposysedit:templatetype)/hipposysedit:prototypes/element(hipposysedit:prototype,myproject:blogpost)

Some document prototypes should however never be present for for example new-document : One of these is for example the document prototype

hippotaxonomy:taxonomy

which is added by the taxonomy project.

It would be easy and handy if a downstream project would be able to suppress its prototype document type from the new-document query without having to use JCR security constraints for it: Using security constraints for example would never work for admin users which have jcr:all everywhere anyway.

Adding 'hippostd:excludePrimaryTypes' to the hippostd:templatequery as below

[hippostd:templatequery] > nt:query
- hippostd:icon (string)
- hippostd:renderer (string)
- hippostd:modify (string) multiple
- hippostd:excludePrimaryTypes (string) multiple
+ hippostd:templates (hippostd:templates) = hippostd:templates

and by default bootstrap it as empty (but present) gives downstream projects the possibility to add a primary type to exclude.