fix: export fossa output even if the script failed

Type of change

• Bug Fix
• Feature
• Pipeline
• Test
• Documentation

Does this introduce a change in the core logic?

• No
• Yes

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Anthos
• Azure
• GCP
• IBM

Does this follow conventional commits spec?

• No
• Yes

Have you set the target Milestone?

• No
• Yes

Have you set the no-detached-pipeline label?

• No
• Yes

Updates description?

Currently, if the fossa-with-cache script fails, the subsequent mv command doesn't execute, and no logs are uploaded for troubleshooting because the fossa-output folder stays inside the app/sdms folder.

This MR fixes it.