(bugfix) (v3.5.1) fix permissions of projects.list file

update-gitweb-access-list had a change recently (289b19d) that had a
side-effect of making projects.list unreadable by other userids (like
'apache' or whatever).

This makes 3.5 unusable for anyone using gitweb.  (Hence the new tag,
too, though 3.5 is only the previous commit and this is a very small
change).
set-default-roles should not kick in always...

should only do its thing when called from someone creating a new wild
repo, and not just changing its perms.  (Because, don't forget, the
POST_CREATE trigger list is invoked from perms also).
'info' should show wild patterns hiding in groups also

(thanks to Sebastian Koslowski for catching this)
set-default-roles: fix bug and add test script
add simple migration instructions to README
partial-copy: remove unused refs

Remove all refs from partial-copy that not longer exists in main.
Also remove all refs from partial-copy that are not longer accessible, due to
changed rights.

Signed-off-by: Jan Weitzel <j.weitzel@phytec.de>
fork command should add hooks from LOCAL_CODE if defined
create command should think of default roles also...

Some code is duplicated from 'set-default-roles' trigger but it's the
cleanest way to fix the problem.
check file/dir existence before locking

check for existence of the object across all branches before creating
the lock.  Helps catch silent typos which may make people think they
locked the file but actually did not.

[code and commit message somewhat edited by committer]
help: include SITE_INFO in output
setup some ENV vars from gitolite.conf options...

makes things much easier in hooks and triggers
v3.5.2