DAST build image stuck on tzdata package requiring console

Summary

Something has changed since the last successful build job causing tzdata to require console input. This blocks all jobs from actually running to completion due to the build job getting stuck.

Steps to reproduce

Create a new branch off master, push it and watch it get stuck:

Setting up tzdata (2020d-1) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Configuring tzdata
------------------
Please select the geographic area in which you live. Subsequent configuration
questions will narrow this down by presenting a list of cities, representing
the time zones in which they are located.
  1. Africa   3. Antarctica  5. Arctic  7. Atlantic  9. Indian    11. US
  2. America  4. Australia   6. Asia    8. Europe    10. Pacific  12. Etc
Geographic area: 

Example Project

https://gitlab.com/gitlab-org/security-products/dast/

What is the current bug behavior?

The build job fails as it is stuck

What is the expected correct behavior?

The build job does not request user input to chose a area you live in.

Relevant logs and/or screenshots

See above

Output of checks

This bug happens on GitLab.com

Possible fixes

Update Dockerfile to contain:

ENV DEBIAN_FRONTEND=noninteractive

More information: https://techoverflow.net/2019/05/18/how-to-fix-configuring-tzdata-interactive-input-when-building-docker-images/