HDDS-4031. Run shell tests in CI

[adoroszlai]

What changes were proposed in this pull request?

1. Add a helper script to run bash test scripts (*.bats).
2. Run bats part of CI.

https://issues.apache.org/jira/browse/HDDS-4031

How was this patch tested?

Created failing test at hadoop-hdds/common/src/test/shell/failing.bats:

@test "fails" {
  [[ "123" == "456" ]]
}

@test "err" {
  asdfs
}

and tested:

$ hadoop-ozone/dev-support/checks/bats.sh
...

$ echo $?
1

$ cat target/bats/summary.txt
not ok 1 fails
# (in test file hadoop-hdds/common/src/test/shell/failing.bats, line 24)
#   `@test "fails" {' failed
not ok 2 err
# (in test file hadoop-hdds/common/src/test/shell/failing.bats, line 29)
#   `asdfs' failed with status 127
# /var/folders/32/sr06nr7123s3bdfsmqsm4pqw0000gn/T/bats-run-70119/bats.70145.src: line 29: asdfs: command not found

$ cat target/bats/failures
2

Passing tests (currently only gc_opts.bat):

1..3
ok 1 Setting Hadoop GC parameters: add GC params for server
ok 2 Setting Hadoop GC parameters: disabled for client
ok 3 Setting Hadoop GC parameters: disabled if GC params are customized

https://github.com/adoroszlai/hadoop-ozone/runs/913609741#step:4:4

[elek]

+1 thanks the patch @adoroszlai

fun fact: I started to do the same during the last weekend, but this patch seems to be better.

As usual, I have some random thoughts added (I think it's good to have "water cooler conversations", and as everybody working from remote, PRs seems to be a good place to chat ;-) )

But none of them are blocker. Especially as I have other PRs with more bats tests, I would prefer to merge it as is, now.

[elek]

discussion-mode:on

This pattern ("fail at the end") is introduced to execute all the tests even if some of them are failing. It's very useful for long and flaky test runs.

But it's somewhat more complex.

Recently I started to think to use a "fail fast" approach. It can simplify the scripts and we can use set -e to be sure we don't ignore any internal errors.

It's not working everywhere, but here it could.

But I am fine with this approach (which is better to create a summary), just sharing my thoughts.

</discussion-mode:on>

[elek]

In the future I am planning to improve all the existing tests:

1. With adding name to all the steps
2. Use upper case for the first letter (default for github actions if the name is missing).

This is the same as the others, so I think we can merge it as is.

[adoroszlai]

Thanks @elek for reviewing and committing it.