The issue is fixed in Visual Studio 2022 version 17.13.2. After updating, the 'Create and Assign Field' quick action follows the naming conventions correctly again. Thanks to @purplecat for pointing this out