clang: Upgrade to 18.1.3

[kraj]

Brings

• c13b7485b879 [clang] Avoid -Wshadow warning when init-capture named same as class field (#74512)
• f249092ef26d [tsan] Refine fstat{,64} interceptors (#86625)
• 76c721994a11 [clang][Sema] Fix a CTAD regression after 42239d2e9 (#86914)
• e0f0c463b539 [mlir][transform] replace original op to loop ops (#83537)
• 47aac495c895 [OpenMP][AIX] Affinity implementation for AIX (#84984)
• a385a917da93 [Support] Fix color handling in formatted_raw_ostream (#86700)
• 0cd4babe0342 Reapply [libcxx] [modules] Fix relative paths with absolute LIBCXX_INSTALL_MODULES_DIR (#86020)
• cfaeee6a8994 release/18.x: [SystemZ] Fix overflow flag for i128 USUBO (#86491)
• 767b61c159b3 [lld/ELF][X86] Respect outSecOff when checking if GOTPCREL can be relaxed (#86334)
• 7c7c3d4a3a27 [ODS][NFC] Cast range.size() to int32_t in accumulation (#85629)
• 0e501dbd932e [Mips] Restore wrong deletion of instruction 'and' in unsigned min/max processing. (#85902)
• fbb27d16fa12 [Mips] Fix missing sign extension in expansion of sub-word atomic max (#77072)
• e74c1678231a [PowerPC] provide CFI for ELF32 to unwind cr2, cr3, cr4 (#83098)
• 1c7c16e58240 [NFC][PowerPC] use script to regenerate the CHECK lines
• c2a57034eff0 [msan] Re-exec with no ASLR if memory layout is incompatible on Linux (#85142)
• b74f6158460c [msan] Add 'MappingDesc::ALLOCATOR' type and check it is available (#85153)
• 98a15dd2d728 [clang][CodeGen] Allow memcpy replace with trivial auto var init
• 2498e3a07f3d [LoongArch] Assume no-op addrspacecasts by default (#82332)
• 368dc8553c5a [SROA]: Only defer trying partial sized ptr or ptr vector types
• 0e16af8e4cf3 [ARM] Update IsRestored for LR based on all returns (#82745)
• 6f8016fda7d5 Pre-commit test showing bug #80287
• ef6d1ec07c69 Bump version to 18.1.3 (#86168)

---

Contributor checklist

• [x] Changes have been tested
• [x] Signed-off-by is present
• [x] The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

• When submitting a review, please pick:
  • 'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
  • 'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
  • 'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)