Hid link to show all logs when all logs were already shown

Resolves #784;

http://jenkins.buttonweavers.com:8080/job/buttonmen-AdmiralJota/422/
I don't like duplication of the logic for how to know which entries to select for action or chat log.  It's especially a problem in the chat log case, where there's some slightly complex logic for grabbing entries from a previous game.

IMO, you should switch to either:
* one SELECT which gets all the entries, puts the first `$logEntryLimit` into an array, counts all of them, and returns both the array and the count, or
* a subroutine which generates the WHERE part of each SQL query, and then the load case adds the limit and the count case turns it into a count

Both of those have efficiency tradeoffs, but i think either way would be better than duplicating code which has to have the same logic to work.