CI: use Ubuntu 22.04

[pwrobeldev]

The CI workflows were running jobs using Ubuntu 20.04.
The mentioned version has been unsupported since 2025-04-15.

Therefore, the workflow files are adjusted to use Ubuntu 22.04.
Moreover, Swift SDK's version is raised from 5.4.3 to 5.7.3, because
the older version is not available for Ubuntu 22.04.

g++ version has been upgraded from 8 to 9, because Ubuntu 22.04
does not support the old package.

[pwrobeldev]

The official communication regarding removal of support for Ubuntu 20.04 from GitHub team can be found here:

• The Ubuntu 20.04 Actions runner image will begin deprecation on 2025-02-01 and will be fully unsupported by 2025-04-15 actions/runner-images#11101

[pwrobeldev]

The minimum supported version of Swift SDK for Ubuntu 22.04 can be found here:

• https://www.swift.org/install/linux/ubuntu/22_04/#latest

Search for "Older releases".

[pwrobeldev]

The problem exists only for Linux. I was trying to reproduce it on macOS, but without success.

The leak reported by valgrind for Linux seems to be false-positive (XCTest ticket linked below). The function responsible for the problem is from XCTest framework:

==4153== 32 bytes in 1 blocks are definitely lost in loss record 1,119 of 3,232
==4153==    at 0x4849013: operator new(unsigned long) (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==4153==    by 0x6995F9C: swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1> >::formWeakReference() (in /usr/lib/swift/linux/libswiftCore.so)
==4153==    by 0x695B127: swift_weakAssign (in /usr/lib/swift/linux/libswiftCore.so)
==4153==    by 0x58710CD: $s6XCTest9XCTWaiterC4wait3for7timeout12enforceOrder4file4lineAC6ResultOSayAA0A11ExpectationCG_SdSbs12StaticStringVSitF (in /usr/lib/swift/linux/libXCTest.so)
==4153==    by 0x58713E8: $s6XCTest9XCTWaiterC4wait3for7timeout12enforceOrder4file4lineAC6ResultOSayAA0A11ExpectationCG_SdSbs12StaticStringVSitFZ (in /usr/lib/swift/linux/libXCTest.so)
==4153==    by 0x585F9F6: $s6XCTest21awaitUsingExpectationyyyyYaKcKF (in /usr/lib/swift/linux/libXCTest.so)
==4153==    by 0x585EE10: $s6XCTest0A4CaseC10invokeTestyyF (in /usr/lib/swift/linux/libXCTest.so)
==4153==    by 0x585EC61: $s6XCTest0A4CaseC7performyyAA0A3RunCF (in /usr/lib/swift/linux/libXCTest.so)
==4153==    by 0x586306F: $s6XCTestAAC3runyyF (in /usr/lib/swift/linux/libXCTest.so)
==4153==    by 0x586156E: $s6XCTest0A5SuiteC7performyyAA0A3RunCF (in /usr/lib/swift/linux/libXCTest.so)
==4153==    by 0x586306F: $s6XCTestAAC3runyyF (in /usr/lib/swift/linux/libXCTest.so)
==4153==    by 0x586156E: $s6XCTest0A5SuiteC7performyyAA0A3RunCF (in /usr/lib/swift/linux/libXCTest.so)
==4153== 
{
   <insert_a_suppression_name_here>
   Memcheck:Leak
   match-leak-kinds: definite
   fun:_Znwm
   fun:_ZN5swift9RefCountsINS_13RefCountBitsTILNS_19RefCountInlinednessE1EEEE17formWeakReferenceEv
   fun:swift_weakAssign
   fun:$s6XCTest9XCTWaiterC4wait3for7timeout12enforceOrder4file4lineAC6ResultOSayAA0A11ExpectationCG_SdSbs12StaticStringVSitF
   fun:$s6XCTest9XCTWaiterC4wait3for7timeout12enforceOrder4file4lineAC6ResultOSayAA0A11ExpectationCG_SdSbs12StaticStringVSitFZ
   fun:$s6XCTest21awaitUsingExpectationyyyyYaKcKF
   fun:$s6XCTest0A4CaseC10invokeTestyyF
   fun:$s6XCTest0A4CaseC7performyyAA0A3RunCF
   fun:$s6XCTestAAC3runyyF
   fun:$s6XCTest0A5SuiteC7performyyAA0A3RunCF
   fun:$s6XCTestAAC3runyyF
   fun:$s6XCTest0A5SuiteC7performyyAA0A3RunCF
}

The same exact problem was reported to XCTest project, but for address sanitizer.

• Running test suites under linux with asan shows a memory leak in xctest swiftlang/swift-corelibs-xctest#342

Please see the following comment:

• Running test suites under linux with asan shows a memory leak in xctest swiftlang/swift-corelibs-xctest#342 (comment)

From the discussion:

Looks like this is a side table being leaked. I’d guess this is a false positive due to the lead sanitizer not recognizing whatever weird bit stuffing we’re doing with the pointer to the side table.