fix: Adjust usage of has_secure_token without a token attr

The behaviour of this method was changed in Rails 7.1, and now
it'll search for a `token` attr in the initialization of the record
instead of the creation. To stay with the same behaviour as before
it's necessary to pass a new argument `on: : create` to the method.

spec/unit/shoulda/matchers/active_record/have_secure_token_matcher_spec.rb

@@ -67,7 +67,11 @@
 
   it 'does not match when missing a token column' do
     create_table(:users)
-    invalid_model = define_model_class(:User) { has_secure_token }
+    invalid_model = if rails_version >= 7.1
+                      define_model_class(:User) { has_secure_token(on: :create) }
+                    else
+                      define_model_class(:User) { has_secure_token }
+                    end
 
     expected_message =
       'Expected User to have :token as a secure token but the following ' \
@@ -125,9 +129,11 @@
 
   it 'does not match when missing a column for a custom attribute' do
     create_table(:users)
-    invalid_model = define_model_class(:User) do
-      has_secure_token(:auth_token)
-    end
+    invalid_model = if rails_version >= 7.1
+                      define_model_class(:User) { has_secure_token(:auth_token, on: :create) }
+                    else
+                      define_model_class(:User) { has_secure_token(:auth_token) }
+                    end
 
     expected_message =
       'Expected User to have :auth_token as a secure token but the ' \