Throw before reaching undefined behavior on AlignedNumber allocation

With this commit, AlignedNumber throws an exception whenever a placement new is made with a misaligned address. This should effectively catch an undefined behavior on the library implementations of operator new() under misaligned addresses.

added bugfix label

requested review from @carsten.graeser

assigned to @santiago.ospina

I'm not sure if I can review this. Is this related to the segfault of debugaligntest that I recently mentioned on matrix? With the same compiler flags this can also be reproduced in the CI, see https://gitlab.dune-project.org/core/dune-common/-/pipelines/75356.

changed the description

I also found the offending placement new but did not understand so far what it does and why it's UB. It seems I have to understand what AlignedNumber exactly does before. Probably looking at your fix supports the understanding. ;-)

added 4 commits

• 426b9bed...5e0b9c2c - 3 commits from branch master
• bc06df47 - Throw before reaching undefined behavior on AlignedNumber allocation

Compare with previous version

requested review from @simon.praetorius and removed review request for @carsten.graeser

added 1 commit

• 13bb2a67 - Throw before reaching undefined behavior on AlignedNumber allocation

Compare with previous version

We need a test/toolchain that triggers the observed problem, right?

added 18 commits

• 13bb2a67...0298f0f7 - 17 commits from branch master
• a2cdcb1f - Throw before reaching undefined behavior on AlignedNumber allocation

Compare with previous version

resolved all threads

merged

mentioned in commit aa5e86be

mentioned in merge request !1505 (merged)

mentioned in merge request !1419