wp_enqueue_script in the editor is a different hook

Scripts for the editing screen do not go on admin_enqueue_scripts — there is a dedicated hook, and using the wrong one loads the editor bundle on every admin page.

// editor only
add_action( 'enqueue_block_editor_assets', function () {
    wp_enqueue_script( 'turkerdev-blocks', /* ... */ );
    wp_enqueue_style( 'turkerdev-blocks-editor', /* ... */ );
} );

// editor AND front end — for the block's own styles
add_action( 'enqueue_block_assets', function () {
    wp_enqueue_style( 'turkerdev-blocks', /* ... */ );
} );

The distinction between the two is the one to internalise: enqueue_block_assets fires in both contexts, which is what you want for the stylesheet that makes the block look the same in the editor as on the page. Registering the style through register_block_type instead means it is only loaded when the block is present, which is better and is not available for the editor half. Getting this wrong is invisible in testing and shows up as a slow admin.