chore: added supoort for backup in update repo api

[Ash-exp]

Description

This PR does the below:

• Better error handling for pipeline material
• create backup for update repository request (payload driven)

Fixes https://github.com/devtron-labs/sprint-tasks/issues/1956

Checklist:

• The title of the PR states what changed and the related issues number (used for the release note).
• Does this PR requires documentation updates?
• I've updated documentation as required by this PR.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have tested it for all user roles.
• I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

Whenever we face an issue in git-sensor, where we need to update the application git-materials to unblock the client, instead of doing that from UI, we should the updated payload as below:

curl --location --request PUT '{{HOST_URL}}/orchestrator/app/material' \
--header 'Content-Type: application/json' \
--header 'Cookie: argocd.token={{TOKEN}}' \
--data '{
    "appId": 1,
    "material": {
        "id": 1,
        "url": "",
        "checkoutPath": "",
        "filterPattern": [],
        "gitProviderId": 2,
        "fetchSubmodules": false,
        "createBackup": true
    }
}'

Here createBackup flag creates the backup of the existing data and then performs the operation. It might take longer than the usual update repository API as it'll copy the directory.

[sonarqubecloud]

Quality Gate failed

Failed conditions
13.9% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud