project-fsck-status.sh: grok --reflog and --indexed-objects

project-fsck-status.sh: grok --reflog and --indexed-objects

Normally Girocco will not have any index files or ref logs in its
repositories.  However, if linked working trees (or even non-bare
repositories) are present either or both are quite possible.

While the "--full" check will indeed always look at index files
and ref logs, the "--no-full" check normally will not.

In fact, even with index files and/or ref logs that refer to objects
that are missing the repository will remain fully clonable by remote
clients.  In most cases that's what it's most useful to have
project-fsck-status.sh looking at -- whether or not the repository
can be successfully cloned by a remote client.

However, it is possible to check ref logs and/or index files when
running in the default "--no-full" mode provided the right options
are passed on down.

Rather than arbitrarily deciding always to check or not check index
files and ref logs in "--no-full" mode, leave the default to not
check them but provide options to enable such checking if desired.

This way the default remains the quickest check and it's only
checking for remote client usability of the repositories, but the
flexibility makes it simple to enable the extra checking when wanted
with the simple addition of one or two options to the cron entry.

Signed-off-by: Kyle J. McKay <mackyle@gmail.com>