AVRO-4022: Add docker CI

[Fokko]

What is the purpose of the change

Adding a test to the docker setup, to ensure that it keeps up to date.

After the changes, it also runs locally on my M3 arm64 mac:

➜  avro git:(fd-run-docker-tests) ✗  build.sh docker-test
...
➜  avro git:(fd-run-docker-tests) ✗  echo $?
0

Currently I only run this on master, since it takes quite a bit to run (40 minutes), or when the Dockerfile is changed.

Verifying this change

(Please pick one of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Extended interop tests to verify consistent valid schema names between SDKs
• Added test that validates that Java throws an AvroRuntimeException on invalid binary data
• Manually verified the change by building the website and checking the new redirect

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[zcsizmadia]

IIRC those exceptions are expected exceptions for checking an unsupported name, but will check later this week. I think the failed test reason is missing libssl package.

[Fokko]

@zcsizmadia Thanks for jumping in here. I was doing some digging myself, and I think you're right. The exceptions are a red herring. It looks like this is because it needs OpenSSL1.1. I think this is part of upgrading Ubuntu to 22 which comes with a newer version of OpenSSL.

[zcsizmadia]

Probably we should remove that exception to the console. It is confusing that it indicates a hard exception.

[Fokko]

Thanks for the quick review @martin-g