🥑🤖 v1.16.0 release prep (aws#600)

* Fix release script prompt when calling from a golang program

For some reason, `read -p` doesn't properly print to stdout when invoked
through golang's `exec.Command().Run()`, but `echo` does. Reading from
stdin still works correctly.

* 🥑🤖 v1.16.0 release prep 🤖🥑

Co-authored-by: ec2-bot 🤖 <ec2-bot@users.noreply.github.com>

🥑🤖 v1.15.0 release prep 🤖🥑 (aws#580)

Co-authored-by: ec2-bot 🤖 <ec2-bot@users.noreply.github.com>

🥑🤖 v1.14.1 release prep 🤖🥑 (aws#565)

Co-authored-by: ec2-bot 🤖 <ec2-bot@users.noreply.github.com>

🥑🤖 v1.14.0 release prep 🤖🥑 (aws#519)

Co-authored-by: ec2-bot 🤖 <ec2-bot@users.noreply.github.com>

🥑🤖 v1.13.4 release prep (aws#512)

* 🥑🤖 v1.13.4 release prep 🤖🥑

* Don't push to Dockerhub during release

* Remove other references to Dockerhub

Co-authored-by: ec2-bot 🤖 <ec2-bot@users.noreply.github.com>

bypass e2e tests because of 1 hour limitation in release pipeline (aw…

…s#482)

Co-authored-by: ec2-bot 🤖 <ec2-bot@users.noreply.github.com>

remove deps (aws#473)

🥑🤖 v1.13.1 release prep 🤖🥑 (aws#454)

Co-authored-by: ec2-bot 🤖 <ec2-bot@users.noreply.github.com>

🥑🤖 v1.13.0 release prep 🤖🥑 (aws#404)

Co-authored-by: ec2-bot 🤖 <ec2-bot@users.noreply.github.com>

🥑🤖 v1.12.2 release prep 🤖🥑 (aws#392)

Co-authored-by: ec2-bot 🤖 <ec2-bot@users.noreply.github.com>