Add PING_TYPE_INSERT

To detect a failure like mysqld can accept a new connection and can respond
a simple select queries, but cannot respond insert/update/delete queries.

In particular, I want to detect hardware trouble (disk failure or RAID
controller failure) and perform fail over automatically.
Merge pull request #40 from kane3/master

Use get_hostinfo() instead of hostname in failover messages
Reformat source code by perltidy -i=2
Merge branch 'feature/ping-insert' of https://github.com/hirose31/mha4mysql-manager
If mysqld accepts queries but hangs on updates
(i.e. RAID controller failure), ping_type=insert causes
duplicate advisory lock failure. This patch prevents the
failure by not acquiring an advisory lock when
checking connections.
Formatting (perltidy -i=2)
Fixing test cases
Merge pull request #41 from hirose31/feature/ping-insert

Add PING_TYPE_INSERT
Merge branch 'master' of https://github.com/yoshinorim/mha4mysql-manager
Rewrite a shebang line of each bin/* scripts if REWRITE_SHEBANG is set

ExtUtils::MakeMaker rewirtes #/usr/bin/perl or #!perl but NOT
#!/usr/bin/env perl, so mandatorily rewrite shebang if environment variable
REWRITE_SHEBANG is set.

- https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker/issues/58
Merge pull request #42 from hirose31/feature/rewrite-shebang

Rewrite a shebang line of each bin/* scripts if REWRITE_SHEBANG is set
Fixing a wrong test case
Releasing 0.56
Use InnoDB for ping insert
Merge pull request #43 from takus/feature/use-innodb-for-ping-insert

Use InnoDB for ping insert