fix: #3573928 setSyncing(TRUE)

prevents changed timestamp updating on Drupal 11.1+

Since Drupal 11.1 (see https://www.drupal.org/node/3250104), calling setSyncing(TRUE) explicitly preserves the original changed timestamp on entity save. This caused the publish and unpublish bulk actions to retain stale changed dates instead of updating them.

Explicitly set the changed time before save in publish() and unpublish() to ensure the changed timestamp reflects when the bulk action was performed.