Fix auth reset logic during redirects to different origin when _base_url set

[MaximZemskov]

What do these changes do?

Do not set ClientSession’s auth during redirects to a different origin when _base_url is set.

Are there changes in behavior for the user?

It might affect users who expect ClientSession to retain auth during redirects to different origins.

Is it a substantial burden for the maintainers to support this?

No.

Related issue number

#6764
#8953

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt
  • The format is <Name> <Surname>.
  • Please keep alphabetical order, the file is sorted by names.
• Add a new news fragment into the CHANGES/ folder

  • name it <issue_or_pr_num>.<type>.rst (e.g. 588.bugfix.rst)

  • if you don't have an issue number, change it to the pull request
    number after creating the PR

    • .bugfix: A bug fix for something the maintainers deemed an
      improper undesired behavior that got corrected to match
      pre-agreed expectations.
    • .feature: A new behavior, public APIs. That sort of stuff.
    • .deprecation: A declaration of future API removals and breaking
      changes in behavior.
    • .breaking: When something public is removed in a breaking way.
      Could be deprecated in an earlier release.
    • .doc: Notable updates to the documentation structure or build
      process.
    • .packaging: Notes for downstreams about unobvious side effects
      and tooling. Changes in the test invocation considerations and
      runtime assumptions.
    • .contrib: Stuff that affects the contributor experience. e.g.
      Running tests, building the docs, setting up the development
      environment.
    • .misc: Changes that are hard to assign to any of the above
      categories.

  • Make sure to use full sentences with correct case and punctuation,
    for example:

    Fixed issue with non-ascii contents in doctest text files
    -- by :user:`contributor-gh-handle`.

    Use the past tense or the present tense a non-imperative mood,
    referring to what's changed compared to the last released version
    of this project.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.28%. Comparing base (51fade1) to head (f854a30).
Report is 4 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #8966   +/-   ##
=======================================
  Coverage   98.28%   98.28%           
=======================================
  Files         107      107           
  Lines       34219    34271   +52     
  Branches     4057     4059    +2     
=======================================
+ Hits        33631    33683   +52     
  Misses        415      415           
  Partials      173      173           

Flag	Coverage Δ
CI-GHA	98.17% <100.00%> (+<0.01%)	⬆️
OS-Linux	97.84% <100.00%> (+<0.01%)	⬆️
OS-Windows	96.24% <100.00%> (+<0.01%)	⬆️
OS-macOS	97.51% <100.00%> (+<0.01%)	⬆️
Py-3.10.11	97.61% <100.00%> (+<0.01%)	⬆️
Py-3.10.14	97.54% <100.00%> (+<0.01%)	⬆️
Py-3.11.9	97.77% <100.00%> (+<0.01%)	⬆️
Py-3.12.5	97.89% <100.00%> (+<0.01%)	⬆️
Py-3.9.13	97.50% <100.00%> (+<0.01%)	⬆️
Py-3.9.19	97.44% <100.00%> (+<0.01%)	⬆️
Py-pypy7.3.16	97.05% <100.00%> (+<0.01%)	⬆️
VM-macos	97.51% <100.00%> (+<0.01%)	⬆️
VM-ubuntu	97.84% <100.00%> (+<0.01%)	⬆️
VM-windows	96.24% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[patchback]

Backport to 3.11: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.11/f569894caa7cfbc2ec03fb5eed6021b9899dc4b4/pr-8966

Backported as #8976

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.