Ventura docs for M2 Macs in this comment: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd?permalink_comment_id=4555340#gistcomment-4555340
Old Monterey docs in this old revision: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd/32c410e3a1de73539c76fa13ea5486569c4e0c5d
Solution for Sonoma: https://gist.github.com/sghiassy/a3927405cf4ffe81242f4ecb01c382ac
This behavior is activation lock and has not changed since T2 and newer chips. The change in Ventura is now MDM enrollment may also persist through wipes (probably via a firmware/Secure Enclave level parameter) and present a similar behavior. I do not have a newer Mac device to test but this seems easy enough to reproduce for anyone that has a newer M-based Mac and wants to use their own MDM solution to test the behavior.
For now a work around would be to use an earlier MacOS for initial install and then upgrade after any network level changes are completed. Once Apple starts releasing Ventura as the base supported OS (such as devices with M2 Pro and beyond) this option will not be available.