Most of the mentioned software probably uses AVX2.I am honestly not sure if I use the benefits of AVX2 -- I always thought that AVX always referred to 1.0 but your post made me do a bit of research, and now I can't really tell if it automatically uses 2. When I had Skylake-X and had AVX-512 it was NEVER used (which was a shame) so I had lumped AVX 2.0 into that category as well.
"AVX" can be confusing, since it can refer to AVX(1) or the whole family (AVX(1), AVX2, AVX-512).
In a way you can view AVX2 as the first full 256-bit SIMD instruction set, while AVX(1) was mostly a partial 256-bit extension of SSE4, but with a new syntax. AVX2 added more operations and flexibility over AVX(1), and added full 256-bit integer support. From a software development perspective, there isn't much use in using AVX(1), since AVX2 is more flexible and complete, only at the expense of dropping support for Sandy Bridge and Ivy Bridge (SB didn't have any good AVX performance anyway). By using AVX2 you usually get the bonus feature of FMA too, which really can accelerate some algorithms.
AVX-512 is unfortunately (to my knowledge) not yet used in consumer software. This is the chicken and the egg problem, as usual. But it's important to get these features widespread so software can start to utilize it. AVX-512 will be massively powerful when we see real applications use it, there will be no going back.