[Task]: When git push fails, show the underlying error instead of throwing a custom Appsmith error

[nidhi-nair]

SubTasks

• Reported error should be traced back to origin
• Appsmith wrapper should still exist, but only to retain the type

[amenasse]

There have been multiple scenarios where this would have been useful for us:

1. Azure Devops depreciated signing algorithms recently. Azure Devops were randomly failing connections using the older signing algorithm. Having the output from the git push would have made it clear what was going on, as they returned a deprecation message when this occurred.

2. Appsmith introduction of atomic commits broke pushes to Azure Devops which doesn't support this feature, without the relevant error in the logs it was hard to track this down.

3. We recently had issues pushing to a branch, it turns out that branch protection had been enabled on the branch but once again it took as a while to realise the underlying issue.