[Fix #51524] Fix strict_loading violations ignored when using pluck

[shes50103]

Motivation / Background

Fixes #51524

Detail

• Update ActiveRecord::Calculations#pluck to raise an error or log on a strict loading violation.
• Update the ActiveRecord::Associations::Association#violates_strict_loading? make preloaded association won't violates strict loading

Additional information

This PR will conflict with #50389 as we are fixing a similar issue in a different scenario.

Checklist

Before submitting the PR make sure the following are checked:

• This Pull Request is related to one change. Unrelated changes should be opened in separate PRs.
• Commit message has a detailed description of what changed and why. If this PR fixes a related issue include it in the commit message. Ex: [Fix #issue-number]
• Tests are added or updated if you fix a bug or add a feature.
• CHANGELOG files are updated for the changed libraries if there is a behavior change or additional feature. Minor bug fixes and documentation changes should not be included.

[shes50103]

I added the find_target? check to ensure that the loaded association adheres to the strict loading rule, which is necessary for passing the newly added test, test_preload_audit_logs_are_strict_loading_with_pluck.

Previously, the violates_strict_loading? method functioned correctly without this check because find_target? was used earlier in the process.

rails/activerecord/lib/active_record/associations/collection_association.rb

Lines 269 to 271 in 82054e8

	if find_target?
	@target = merge_target_lists(find_target, target)
	end

rails/activerecord/lib/active_record/associations/association.rb

Lines 220 to 223 in 82054e8

	def find_target
	if violates_strict_loading?
	Base.strict_loading_violation!(owner: owner.class, reflection: reflection)
	end

I'm not sure whether to open a separate PR for this refactoring since it's a minor change. For now, I've added it as a second commit.