Extended docs with logging customisation at runtime

[ElenaKhaustova]

Description

Solves https://github.com/kedro-org/kedro/issues/3918

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

• [x] Read the contributing guidelines
• [x] Signed off each commit with a Developer Certificate of Origin (DCO)
• [x] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• [x] Updated the documentation to reflect the code changes
• [x] Added a description of this change in the RELEASE.md file
• [ ] Added tests to cover my changes
• [ ] Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

[ElenaKhaustova]

Some stylistic soft suggestions - I also wonder if it's worth listing out the other other class paths we may want to tell the user they can quieten 🤔

I have applied the suggestions, thank you!

As for the other class paths, do you have any in mind that are worth adding or about which we have complaints? Overall, adding another path should be straightforward now even with this example.