fix: Ensure pending condition is always preserved

[shorim]

Description

Changes proposed in this pull request (what was done and why):

• Ensure that the Pending condition always exists in the conditions list for TracePipeline, LogPipeline and LogParser
• If a pipeline was in a pending condition and then it becomes deployable, this will result in the Trace Gateway / Fluent Bit to restart. Therefore, when handling the running condition, we can always set the reason for the false pending condition to be FluentBitDaemonSetNotReady for LogPipeline and TraceGatewayDeploymentNotReady for TracePipeline
• Rename SetRunningCondition func to HandleRunningCondition to avoid giving the false impression that it only sets the Running condition to True
• Rename SetPendingCondition func to HandlePendingCondition to avoid giving the false impression that it only sets the Pending condition to True
• Updated unit tests
• Updated e2e test verifiers

Changes refer to particular issues, PRs or documents:

• Relates to Introduce new status API for logs and traces, mark the old one as deprecated #805

Traceability

• The PR is linked to a GitHub issue.
• New features have a milestone set.
• New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
• The corresponding GitHub issue has a respective area and kind label.
• The follow-up issues (if any) are linked in the Related Issues section.
• Adjusted the documentation if the change is user-facing.
• The feature is unit-tested
• The feature is e2e-tested