The statuses of the CRs should be updated when got errors during the reconciling

[ywk253100]

Currently, some of the controllers only log the errors rather than update them into the status of CRs, this causes

1. Confuse, users don't know what happened to the CR as the status is stuck in in-progress
2. Hard to debug, need to check the logs to find out what happened
3. Hard for the downstream projects to integrate because the downstream projects may depend on the status to decide what is the next step.

For example, if the BSL is unavailable, the DeleteBackupRequest is stuck in InProgress status

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "I would like to see this bug fixed as soon as possible"
• 👎 for "There are more important bugs to focus on right now"

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue was closed because it has been stalled for 14 days with no activity.

[kaovilai]

Perhaps this should be added to or follow up to #7207? or have this be epic containing #7207