move_on_after / fail_after not immediately entered

See https://github.com/python-trio/trio/issues/2512 and https://github.com/python-trio/trio/pull/3010

The PR discussion suggests gating it on currently running Trio version, I personally think that's too prone to missed errors and should instead always warn - but prominently mention that you should disable the check if you only support new Trio versions.