Use #!/usr/bin/env bash in get-info.sh to support macOS users

[cisaacstern]

get-info.sh uses the mapfile command

pangeo-forge-gcs-bakery/scripts/get-info.sh

Line 23 in 5ee5287

mapfile -t < <(kubectl logs -n "$BAKERY_NAMESPACE" deployment/prefect-agent | sed -En "s/\[([0-9]+-[0-9]+-[0-9]+) ([0-9]+:[0-9]+:[0-9]+).* agent \| Completed deployment of flow run (.*)/\1@\2-\3/p")

This does not work out-of-the-box on macOS, because even the latest Macs (mine is about ~2 months old) ship with system bash as bash 3, but mapfile was introduced in bash 4. 👈 This linked issue recommends upgrading bash with homebrew and then sudo mv /usr/local/bin/bash /bin/bash. This solution might work in a GitHub Workflows context, but on an actual MacBook, write access to /bin is blocked (even for root users) by security features which are cumbersome to circumvent.

For executing scripts with user-installed versions of bash, this tutorial recommends the #!/usr/bin/env bash syntax added in this PR. I contemplated replacing #!/bin/bash with this in all of the scripts for consistency, but thought it would be better to only make the minimal required change.

I am going to add a check for bash version to this PR, so the code self-documents why we are doing this, and then I will open for review.

xref #19 (b/c this issue arose as part of that work)

[cisaacstern]

I am going to add a check for bash version to this PR, so the code self-documents why we are doing this, and then I will open for review.

All set! Opening for review now.

[tracetechnical]

May be worth adding "which bash" to get the bash dir, incase someone has something funky going on.

[tracetechnical]

That said... the hashbang is pretty explicit about where to find bash.. so I revoke my previous comment