fix: Use deepcopy with exceptions instead of deepcopy

[sjrl]

Related Issues

• fixes BreakpointConfirmationStrategy fails to serialize Components with thread locks #394

Proposed Changes:

When creating a pipeline snapshot we make sure to use _deepcopy_with_exceptions when copying component inputs to avoid deep copies of items like components and tools since they often contain attributes that are not deep-copyable. For example, the LinkContentFetchter has httpx.Client as an attribute which throws an error if we try to deep copy it.

How did you test it?

Notes for the reviewer

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[anakin87]

Thanks

[coveralls]

Pull Request Test Coverage Report for Build 19425414790

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 6 unchanged lines in 1 file lost coverage.
• Overall coverage remained the same at 71.356%

---

Files with Coverage Reduction	New Missed Lines	%
core/pipeline/breakpoint.py	6	54.55%

Totals
Change from base Build 19425407698:	0.0%
Covered Lines:	1126
Relevant Lines:	1578

---

💛 - Coveralls