Update CPU Architectures, Update YATeTo

[davschneller]

• Adds several new CPU architectures, as shown in YATeTo right now (but not yet apple-m2). Also adds dummy architectures for SVE and NEON.
• Splits between ALIGNMENT and VECTORSIZE. The latter, VECTORSIZE should equal the YaTeTo value; it's from now on used in calculating any aligned reals or basis functions. The former value, ALIGNMENT may be larger (e.g. as large as a cache line), but mostly, it's still the same value.
• Updates YATeTo. That also includes Remove some deepcop[ies] to speed up strengthReduction yateto#66 , and by that a significant speed improvement for the kernel generation.
• Reworks the GEMM_TOOLS_LIST=auto option to include LIBXSMM_JIT before LIBXSMM, and the new architectures. Also, all of these programs need to be found by CMake before they are considered for auto. Eigen is now always added at the end in this case.
• Redzone is now disabled by default (especially for noarch), and enabled for most X86_64 CPUs again.

[davschneller]

Maybe also related to #960 . (i.e. the split between ALIGNMENT and VECTORSIZE)

[codecov-commenter]

Codecov Report

Merging #962 (c83b8d9) into master (1579dfa) will not change coverage.
Report is 2 commits behind head on master.
The diff coverage is 0.00%.

❗ Current head c83b8d9 differs from pull request most recent head 6a1eb0e. Consider uploading reports for the commit 6a1eb0e to get more accurate results

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

@@           Coverage Diff           @@
##           master     #962   +/-   ##
=======================================
  Coverage   14.39%   14.39%           
=======================================
  Files         253      253           
  Lines       14223    14223           
=======================================
  Hits         2047     2047           
  Misses      12176    12176           

Files	Coverage Δ
src/Kernels/common.hpp	0.00% <0.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[sebwolf-de]

Should we then also change the variable name to i_vectorsize?

[krenzland]

IMO no, because it is an alignment (to vectorsize)

[krenzland]

(same below)

[davschneller]

Ok, I've left it that way for now—since even though it's VECTORSIZE, we're aligning everything. Instead, we may have to rename the ALIGNMENT variable soon, I'd guess. And also, make both of them a C++ constexpr maybe.

I've also cleaned up the file a bit (i.e. remove i_ etc.) and templated the functions with the size of the reals used. ... That could also become a parameter instead.

[sebwolf-de]

Change variable name?

[sebwolf-de]

Change variable name?