[compiler-rt][tysan] False positives with vtable pointer initialization

# static or global variables with `vtable`
#### Flags: `-stdlib=libc++ -fsanitize=type -O0`
#### Compiler: x86-64 clang 22.1.0
#### Link: https://godbolt.org/z/1f9na6h36
#### Code:
```.cpp
class A {
public:
virtual ~A() = default;
char byte;
};

static A a;

int main() {}
```
#### Logs:
```
==1==ERROR: TypeSanitizer: type-aliasing-violation on address 0x5f724336cee8 (pc 0x5f7242a12067 bp 0x7ffeec53b2a0 sp 0x7ffeec53b230 tid 1)
WRITE of size 8 at 0x5f724336cee8 with type vtable pointer accesses an existing object of type A
#0 0x5f7242a12066 (/app/output.s+0x36066)
```
#### Explanation:
Likely a static lifetime + virtual object initialization. Removal of `byte` variable does not reproduce.

Start by reproducing the minimal C++ example with the listed libc++, TypeSanitizer, optimization, and x86-64 settings, using the linked Compiler Explorer case. Trace the static object's virtual initialization and the reported vtable-pointer access. Done means this example no longer reports a type-aliasing violation while the sanitizer's valid diagnostics remain covered by an appropriate regression test.

Written by the indexing model from the issue text.