fix: serialize/deserialize torch dtype in the components that need it

[anakin87]

Related Issues

• fixes Dumping a Pipeline to yaml is broken for certain kwargs #6671

Proposed Changes:

• In each affected component, convert the torch.dtype parameters to string during serializaion.
• Convert back to torch.dtype during deserialization

How did you test it?

CI, extended unit tests, new tests

Notes for the reviewer

If you feel that there is too much code duplication, I can put the serialization/deserialization logic into a utility function.

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

[coveralls]

Pull Request Test Coverage Report for Build 7501213766

Warning: This coverage report may be inaccurate.

We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.05%) to 87.121%

---

Totals
Change from base Build 7490996754:	0.05%
Covered Lines:	4282
Relevant Lines:	4915

---

💛 - Coveralls

[masci]

Left one comment that's not actually related to the main point of the PR.

About code duplication, having similar code across 3 components I think it's fine, we can extract common utilities as we need them for more components.