Fix Provision JDK step for Linux on CI

[jfversluis]

This change adds the --force-confdef switch to the dpkg that happens while provisioning the JDK on Linux. This means that the default option is selected when interactive feedback is requested. In our case at the time of writing, this was the output that would hang the builds:

Task "Exec"
         Task Parameter:Command=sudo dpkg -i packages-microsoft-prod.deb
         sudo dpkg -i packages-microsoft-prod.deb
         (Reading database ... 295979 files and directories currently installed.)
         Preparing to unpack packages-microsoft-prod.deb ...
         Unpacking packages-microsoft-prod (1.2-ubuntu22.04) over (1.0-ubuntu22.04.1) ...
         Setting up packages-microsoft-prod (1.2-ubuntu22.04) ...
         
         Configuration file '/etc/apt/sources.list.d/microsoft-prod.list'
          ==> Modified (by you or by a script) since installation.
          ==> Package distributor has shipped an updated version.
            What would you like to do about it ?  Your options are:
             Y or I  : install the package maintainer's version
             N or O  : keep your currently-installed version
               D     : show the differences between the versions
               Z     : start a shell to examine the situation
          The default action is to keep your current version.

With this switch, the default action (in this case N, keep currently installed version) is selected.

[Copilot]

Pull Request Overview

This PR fixes a CI build hang issue on Linux by adding the --force-confdef flag to the dpkg command used during JDK provisioning. The change ensures that when dpkg encounters configuration file conflicts, it automatically selects the default option (keeping the currently installed version) instead of waiting for interactive user input.

• Modifies the dpkg command to include --force-confdef flag for non-interactive operation
• Prevents CI builds from hanging when configuration file conflicts occur during package installation