Use Chewy.thread_local_data to access Thread.current

[bolshakov]

Currently, it's dangerous to use Chewy with dry-effects, because it runs fibers that reset Thread local state. This PR isolates thread-local variables access, so it could be easily extended.

After isolating them, we can provide dry-effects integration.

See https://github.com/dry-rb/dry-effects/issues/82 for the details.

Before submitting the PR make sure the following are checked:

• [x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
• [x] Wrote good commit messages.
• [x] Commit message starts with [Fix #issue-number] (if the related issue exists).
• [x] Feature branch is up-to-date with master (if not - rebase it).
• [x] Squashed related commits together.
• [x] Added tests.
• [x] Added an entry to the changelog if the new code introduces user-observable changes. See changelog entry format for details.