The AD version did just pop up out of nowhere for most people.
For the majority of LAPS users who don’t read details of each months Windows Updates and are not following this thread, they still don't know and won’t notice until their legacy LAPS client installs and MDT task sequences start failing. They may not even notice that their new legacy LAPS clients installed on top of the April updates are not working.
Even for the people who do follow this, it’s a scramble to make changes on very short notice before the April updates get pushed out in the organization.
It probably would have been better that it didn’t just take over the legacy policies without action and required that you proactively configure new AD group policy settings to start using the built-in LAPS client.