fix: Fix Pipeline.run() getting stuck in a loop even though there are components that can run

[silvanocerza]

Related Issues

• related to [2.0.0b8] Generator is being called twice instead of once after loading the pipeline yaml file #7243

Proposed Changes:

Add a missing check in Pipeline.run() that prevented Components with only default inputs to run when the Pipeline is stuck in a loop.

How did you test it?

I ran the failing end to end test that was failing.

Notes for the reviewer

No need for release notes as the bug was created with #7426 and it still has not been released.

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 8465791582

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.
• 4 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.05%) to 89.532%

---

Files with Coverage Reduction	New Missed Lines	%
core/pipeline/pipeline.py	4	93.85%

Totals
Change from base Build 8450062887:	0.05%
Covered Lines:	5568
Relevant Lines:	6219

---

💛 - Coveralls

[masci]

LGTM