[S] Change in coreboot[main]: soc/mt6366: Work around GCC LTO build

[Yu-Ping Wu (Code Review)]

Attention is currently required from: Arthur Heymans, Cliff Huang, Elyes Haouas, Hung-Te Lin, Julius Werner, Jérémy Compostella, Lance Zhao, Tim Wawrzynczak, Yidi Lin.

Yu-Ping Wu has posted comments on this change by Arthur Heymans. ( https://review.coreboot.org/c/coreboot/+/84208?usp=email )

Change subject: soc/mt6366: Work around GCC LTO build
......................................................................

Patch Set 8:

(1 comment)

File src/soc/mediatek/mt8186/mt6366.c:

https://review.coreboot.org/c/coreboot/+/84208/comment/51c9b13b_cd18dea0?usp... :
PS8, Line 10: #define NO_BUILDTIME_ASSERT
> It looks like this is only a problem with very specific assert statements, so if we do want to hack  […]

Code like

```
assert(vddq_uv >= 530000);
ASSERT_LTO_WORKAROUND(vddq_uv <= 680000);
```

seems pretty weird and inconsistent, and the `ASSERT_LTO_WORKAROUND` solution doesn't seem robust. For now, only the 2nd call needs to be workarounded because there's some other code that sets the voltage to be greater than 680000 for a non-VDDQ regulator type. That means, future code changes (outside this file) are likely to break the 1st assert call with LTO, and when that happens we'll also need to change it to `ASSERT_LTO_WORKAROUND`. Therefore I'd prefer defining `NO_BUILDTIME_ASSERT` for the whole file, to avoid any potential future issues.