Fix tapenade 3.16 to a specific build version, and update Ubuntu runners to U22.04

[eirikurj]

Purpose

Currently, we are using the latest Tapenade version when running the checks on Azure. However, this might not be the most stable approach, as they seem to be generating releases/updates directly from develop branch, setting it as the latest 3.16 to download. A floating version like this will fail the tests, as the header in the differentiated files will at minimum change. Furthermore, Tapenade has been silently failing, causing false positives (see recent build logs).

This PR fixes the 3.16 version to a specific build tapenade_3.16-v2-123-gcc03863c3. This version is chosen since more recent versions append *4 to an integer declaration in reverse mode codes. See discussion on this here mdolab/idwarp#82 (comment)

The build environment is also updated to U22.04 due to a GLIBC_2.34 error on U20.04. To keep consistency, the same is done for other build environments.

Expected time until merged

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (non-backwards-compatible fix or feature)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Documentation update
• Maintenance update
• Other (please describe)

Testing

Checklist

• I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
• I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
• I have run unit and regression tests which pass locally with my changes
• I have added new tests that prove my fix is effective or that my feature works
• I have added necessary documentation

[sseraj]

The changes look good. Nice catch on the GLIBC error. Maybe we should update all the vmImages to U22?

[eirikurj]

Yeah, we should do that. Will push an update shortly and update the PR description.