tests: don't hardcode path to bash interpreter

Use the env binary to figure out the correct bash to use.
Certain systems ships with an ancient version of bash, but the
user might have installed a newer one that is earlier in $PATH.

For example the current version of Mac OS X ships version 3.2.51
of bash, which does not understand new fancy builtins such as
readarray. A user might install a newer version of bash, use that
as their shell and add that path before bin.

tests/bundles/rebase.sh

@@ -1,44 +1,44 b''
-#!/bin/bash
+#!/usr/bin/env bash
 hg init rebase
 cd rebase
 
 #  @  7: 'H'
 #  |
 #  | o  6: 'G'
 #  |/|
 #  o |  5: 'F'
 #  | |
 #  | o  4: 'E'
 #  |/
 #  | o  3: 'D'
 #  | |
 #  | o  2: 'C'
 #  | |
 #  | o  1: 'B'
 #  |/
 #  o  0: 'A'
 
 echo A > A
 hg ci -Am A
 echo B > B
 hg ci -Am B
 echo C > C
 hg ci -Am C
 echo D > D
 hg ci -Am D
 hg up -q -C 0
 echo E > E
 hg ci -Am E
 hg up -q -C 0
 echo F > F
 hg ci -Am F
 hg merge -r 4
 hg ci -m G
 hg up -q -C 5
 echo H > H
 hg ci -Am H
 
 hg bundle -a ../rebase.hg
 
 cd ..
 rm -Rf rebase

tests/bundles/remote.sh

@@ -1,32 +1,32 b''
-#!/bin/bash
+#!/usr/bin/env bash
 hg init remote
 cd remote
 
 echo "0" >> afile
 hg add afile
 hg commit -m "0.0"
 echo "1" >> afile
 hg commit -m "0.1"
 echo "2" >> afile
 hg commit -m "0.2"
 echo "3" >> afile
 hg commit -m "0.3"
 hg update -C 0
 echo "1" >> afile
 hg commit -m "1.1"
 echo "2" >> afile
 hg commit -m "1.2"
 echo "a line" > fred
 echo "3" >> afile
 hg add fred
 hg commit -m "1.3"
 hg mv afile adifferentfile
 hg commit -m "1.3m"
 hg update -C 3
 hg mv afile anotherfile
 hg commit -m "0.3m"
 
 hg bundle -a ../remote.hg
 
 cd ..
 rm -Rf remote