LLDB bridge oddities

This is an umbrella bug to document and track found irregularities in LLDB and/or its bridge:

• LLDB bridge reports incorrect alignment for some std container types (at least std::string and std::list, but probably more). Usually 1 whereas 8 is expected. This causes issues when alignment requirements are used to interpret raw data, most prominent example is std::map. See also QTCREATORBUG-32309.
• If there are multiple anonymous structs around they can get mixed up. See AnonymousStruct and Gdb10586eclipse debugger dumper tests as examples.
• LLDB bridge reports incorrect size of exactly 0 for std::pmr::polymorphic_allocator<std::pair<const int, int>> (should be at least 8 due to a pointer to the memory resource stored inside). See QTCREATORBUG-30224 as well.

Other debug bridges (i.e. CDB and GDB) do not seem to be affected.

Note, there are certain debugger dumper autotests disabled due to these issues. Searching the code for this ticket's number should be a good starting point in identifying such tests. If any of the above issues are fixed, please re-enable the respective tests.