Fixing DBeaver driver issues on T2+ SREs

[craddm]

✅ Checklist

• You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
• You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
• Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).
• You have marked this pull request as a draft and added '[WIP]' to the title if needed (if you're not yet ready to merge).
• You have formatted your code using appropriate automated tools (for example ./tests/AutoFormat_Powershell.ps1 -TargetPath <path to file or directory> for Powershell).

⤴️ Summary

1. Updates VM image building process so that drivers are installed in an appropriate place. The default folder for DBeaver changed from usr/share/dbeaver/ to /usr/share/dbeaver-ce/, so modifications to the ini file were not correctly applied.
2. Adds new driver for PostgreSQL that was not previously installed.
3. Updates the VM image in the reference configs to one with a fully working version of DBeaver
4. Updates docs for database usage to show the driver download dialog boxes that can appear.

Note that this new VM image also includes an up-to-date version of Julia, which address a non-DBeaver related issue.

🌂 Related issues

Closes #1666
Closes #1679 since this also updates Julia to 1.10, which will automatically handle changes in CPU architecture. Thus tests will no longer fail on AMD CPUs.

🔬 Tests

Built a new VM image, deployed it to a Tier 2 SRE, and successfully connected to MSSQL and PostgreSQL databases from the T2 SRE.

Rebuilt docs locally

[JimMadge]

Looks good 👍.

Great work @craddm.