move triggers into their own subdir...

...otherwise 'gitolite help' was getting too confusing, mixing up stuff
that users should not be running directly (even on the server)

----

implementation notes:

those who are worried about the '../triggers/' in various parts of the
code here, remember you can only do that from a command line on the
server.  Remote users can only use commands that have been explicitly
listed in the COMMANDS hash in the rc file.  This means they can't even
access other commands in the same directory as, say, the 'info' command,
so a '../' is definitely not going to work.

src/commands/post-compile/update-gitweb-access-list

@@ -1,15 +0,0 @@
-#!/bin/sh
-
-# this is literally the simplest gitweb update possible.  You are free to add
-# whatever you want and contribute it back, as long as it is upward
-# compatible.
-
-plf=$(gitolite query-rc GITWEB_PROJECTS_LIST)
-[ -z "$plf" ] && plf=$HOME/projects.list
-
-(
-    gitolite list-phy-repos | gitolite access % gitweb R any | grep -v DENIED
-    gitolite list-phy-repos | gitolite git-config -r % gitweb\\.
-) |
-    cut -f1 | sort -u | sed -e 's/$/.git/' > $plf
-