[DOC] Add complex chaining example using pipelines with builder pattern

[zion-off]

Pull Request check-list

Please make sure to review and check all of these items:

• Do tests and lints pass with this change?
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
• Is the new or changed code fully tested?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Is there an example added to the examples folder (if applicable)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

Description of change

This PR adds an example of using the builder pattern for to chain complex pipeline operations.

See #1744.

[petyaslavova]

Hi @zion-off, thank you for your contribution!

[Copilot]

Pull Request Overview

This PR adds a comprehensive example demonstrating the builder pattern for chaining complex Redis pipeline operations, helping users understand how to implement fluent interfaces with Redis pipelines.

• Adds a new notebook cell with an advanced chaining example using custom repository class
• Implements a RedisRepository class that uses the builder pattern for method chaining
• Demonstrates real-world usage with User and Post dataclasses for a social media-like application

Comments suppressed due to low confidence (3)

docs/examples/pipeline_examples.ipynb:1

• Using post.title[0] as a key component will cause collisions when multiple posts have titles starting with the same character. Consider using a unique identifier like a UUID or incrementing counter instead.

{

docs/examples/pipeline_examples.ipynb:1

• Using post.title[0] as a key component will cause collisions when multiple posts have titles starting with the same character. Consider using a unique identifier like a UUID or incrementing counter instead.

{

docs/examples/pipeline_examples.ipynb:1

• This code could raise an IndexError if the email doesn't contain '@'. Consider adding validation or using a more robust email parsing approach for the example.

{

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[petyaslavova]

Overall, it looks fine; you just need to apply the suggested improvements, and it will be ready for merging.

[zion-off]

hi @petyaslavova, thanks so much for your review! i've amended my commit with your suggestion. just @ me if you'd like me to modify anything else!

[petyaslavova]

LGTM.