The question is the opposite: you have to prove to managers the benefit overcomes the risk of using a new language. Rust is still not nearly stable nor popular enough for many fields.
Go is a very different language with different goals and constraints, so the question does not really fit.
> Rust and Go are much simpler to learn
Go is a simple language, yes. Rust is a different beast with the same intrinsic complexity as C++.
> can do everything that C++
Not exactly true (for the moment). Rust is lacking on const generics, HKTs and other details.
> sane, simple and clean build systems/package managers
That is not a big argument for the kind of projects is used for.
And it is not true either, since nowadays there are several competing, modern package managers for C++ too (build2, Meson, Conan, modern CMake...).
> not to mention async/await concurrency
The async IO model has been available in many languages for many years, including C++. In the recent years several languages (including Rust and C++) are bringing syntax sugar to let the compiler create the state machines. But it is not the only way of doing async.