refactor: read touch_update_defaults? from options instead of changeset context

Read the touch_update_defaults? flag from the bulk_create options map
rather than from changeset context.

Depends on ash-project/ash#2590 which adds touch_update_defaults? to the
options passed to data layers. Only merge once that PR is merged and released.

Author: mbaertschi

lib/data_layer.ex

@@ -2382,9 +2382,8 @@ defmodule AshPostgres.DataLayer do
           # Include fields with update_defaults (e.g. update_timestamp)
           # even if they aren't in the changeset attributes or upsert_fields.
           # These fields should always be refreshed when an upsert modifies fields.
-          # Can be disabled via context: %{data_layer: %{touch_update_defaults?: false}}
-          touch_update_defaults? =
-            Enum.at(changesets, 0).context[:data_layer][:touch_update_defaults?] != false
+          # Can be disabled via touch_update_defaults?: false option
+          touch_update_defaults? = Map.get(options, :touch_update_defaults?, true)
 
           if touch_update_defaults? do
             update_default_fields =

test/bulk_create_test.exs

@@ -224,7 +224,7 @@ defmodule AshPostgres.BulkCreateTest do
                  upsert?: true,
                  upsert_identity: :uniq_one_and_two,
                  upsert_fields: [:price],
-                 context: %{data_layer: %{touch_update_defaults?: false}},
+                 touch_update_defaults?: false,
                  return_stream?: true,
                  return_errors?: true,
                  return_records?: true