Fix CI workflows, compiler flags, and flaky tests

[bmehta001]

CI/build/test fixes only — no runtime behavior changes. Runtime fixes (data races, memory leak, shutdown safety) are in #1429.

Modernize CI workflows (11 files)

• Update all GitHub Actions to latest versions (checkout@v4, setup-java@v5, setup-android@v3, etc.)
• Add concurrency groups with cancel-in-progress scoped to pull_request events only — push builds on main always run to completion so a rapid second push can't hide a broken commit
• Add 30-minute timeout-minutes to iOS CI to prevent deadlock hangs (the CancelAllRequests spin loop can hang indefinitely if an NSURLSession completion handler never fires on the simulator)
• Fix iOS simulator destination: resolve simulator UUID via xcrun simctl list to avoid ambiguous -destination matching
• Fix Android SDK path detection in CodeQL workflow

Fix compiler flags (2 files)

• Split GCC and Clang warning flags — -Wno-unknown-warning-option is Clang-only and was breaking GCC builds
• Add -fno-finite-math-only to all non-MSVC release flags — restores IEEE 754 compliance (INFINITY macro) needed by sqlite3 and tests when -ffast-math is enabled
• Remove global -Wno-reorder, scope to Sanitizer.cpp only via set_source_files_properties — the only file that triggers the warning is in the lib/modules submodule where Sanitizer.hpp declares members in a different order than the constructor init list

Improve iOS test script and documentation (3 files)

• Rewrite build-tests-ios.sh to dynamically resolve simulator UUID for unambiguous xcodebuild destination
• Document python3 requirement in README
• Update docs/cpp-start-ios.md with current build instructions

Fix flaky functional tests (6 files)

• Unique phase2 DB paths (APITest.cpp): replace PAL::sleep(500) with unique-per-invocation DB paths using an atomic counter. The SDK closes SQLite via sqlite3_close_v2() which defers file-descriptor cleanup — reusing a fixed path and std::remove()-ing files with deferred fds still open caused iOS vnode unlinked while in use errors
• SQLite journal cleanup (APITest.cpp, AISendTests.cpp): remove -wal, -shm, -journal files in CleanStorage() to prevent cross-test contamination
• Config contamination (BasicFuncTests.cpp): reset CFG_INT_CACHE_FILE_SIZE and CFG_INT_STORAGE_FULL_PCT in test Initialize() — LogManager::GetLogConfiguration() returns a global singleton, so tests that modify config fields contaminate subsequent tests
• yield() → sleep(10) (BasicFuncTests.cpp): reduces CPU contention on single-core iOS simulator runners and gives the network stack time to deliver
• Multi-batch upload flakiness (BasicFuncTests.cpp): add SetTransmitProfile(TransmitProfile_RealTime) before UploadNow() to set all timer delays to 0 — prevents events from being held back in lower-priority batches
• Use 127.0.0.1 (BasicFuncTests.cpp): replace localhost with 127.0.0.1 for the local test HTTP server — avoids DNS resolution failures on iOS simulator
• Increased timeouts: widen waitForEvents timeouts across tests to accommodate slow CI runners
• Atomic counter (MultipleLogManagersTests.cpp): fix data race on shared event counter

[lalitb]

for the comments.

[lalitb]

@bmehta001 - The CI fixes are important and also more safe, but this PR also changes some runtime behavior in the HTTP client, WorkerThread, TPM, Logger, and HttpResponseDecoder.

Can we keep this PR scoped to the CI/build/test fixes, and move the runtime race/shutdown fixes to a separate PR? If any of these runtime changes are needed to unblock CI, can you call that out with the specific failure they address and how it was validated?

[bmehta001]

@lalitb - Yes, will remove all functional changes to put in another PR, even if a few tests fail in the CI on this branch, just to keep things simple.

[lalitb]

Thanks @bmehta001 - Nice work, Appreciate making the CI green!