Improve strict_loading documentation [ci skip]

[ansonhoyt]

• Update ActiveRecord::StrictLoadingViolationError API docs to
  reference the guide to help beginners learn how to resolve the error.
• Update Active Record Query Interface guide to cover configuration and
  the association option.

Motivation / Background

This Pull Request has been created to improve the docs and guides.

Detail

This Pull Request changes:

1. ActiveRecord::StrictLoadingViolationError API docs to link to the guide.
2. Active Record Query Interface guide to cover other facets of strict_loading.

Additional information

Explains the association option, highlighted in Chris Oliver's excellent Rails World talk Powerful Rails Features You Might Not Know.

Continues the nice additions in #49329

I was inspired by @zzak's comment on #49741

Checklist

Before submitting the PR make sure the following are checked:

• This Pull Request is related to one change. Changes that are unrelated 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.

[ansonhoyt]

The API Documentation Guidelines' Links section doesn't cover when or how we should link to the guides from API docs.

I think it would help me if I got this error, but I couldn't find any existing links from API docs to Guides, so let me know if I did a bad thing 😬

[eileencodes]

Thanks, can you squash your commits into one commit?

[ansonhoyt]

@eileencodes Done! Thanks for bearing with my Codespaces learning curve.

P.S. I enjoyed your talk The Magic of Rails. It piqued my curiosity to explore Active Storage code as I write a small API client.

[zzak]

Thanks for working on this! Good additions. 👏

The API Documentation Guidelines' Links section doesn't cover when or how we should link to the guides from API docs.

I think it would help me if I got this error, but I couldn't find any existing links from API docs to Guides, so let me know if I did a bad thing 😬

There is a tiny blurb about it here, if you mean what I think you mean:
https://edgeguides.rubyonrails.org/ruby_on_rails_guides_guidelines.html#linking-to-the-api

In short, api. and guides. get turned into edge* during generation. So we don't have to type "edge" unless we really mean it.