Expect user-defined QT_NO_INT128 in removed_api.cpp


We currently don't support building Qt with GCC and -ansi (or
-std=c++NN as opposed to -std=gnu++NN), because in that mode, the
language still recognizes __int128_t, but the C++ standard library
does not, leading to bloopers such as std::is_integral_v<__int128_t>
== false or std::is_signed_v<__int128_t> == false, or simply
std::numerical_limits<__int128_t> not being properly specialized.

But we do have QT_NO_INT128, which, when defined, disables all the Qt
extended integer support.

A user requested to allow compiling with -ansi again, to which I
responded that they should define QT_NO_INT128 then, too, but, of
course, the unconditional #define in bluetooth/removed_api.cpp would
cause a redefinition warning.

So fix the code to use a conditional #define.

Amends 5d90296f312f72ffa6a5322df7b565c3e5521684.

Pick-to: 6.10 6.9 6.8
Task-number: QTBUG-139280
Change-Id: I0e453270bea883e995b0cb058bf15111b6f3adc8
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
commit195802c240ed184a82c6140aba917f0b823f9d87
parent91d00f8bec1a7b137ca344796c8fe0ad1adea62f
authorMarc Mutz <marc.mutz@qt.io>
committerIvan Solovev <ivan.solovev@qt.io>
commit timeTue, 9 Sep 2025 07:52:29 +0000