Create meaningful error messages by encapsulating backend server errors for Ratify Users

[yizha1]

This issue was created to track the following comment:

          Passing through errors is not a user-friendly practice. We need to catch the error from ACR and wrap it into something meaningful\ for the user of Rarify. The user of Ratify may have no knowledge of where the artifact is and even not know what artifact descriptor is. We need to provide meaningful message for the user of Ratyify and not the user of ACR.

Originally posted by @toddysm in #1662 (comment)

[Horiodino]

Hey @yizha1 , I'd be happy to work on this if no one else is currently handling it. If there's anything else I can do, or if you have any documentation or references that could help resolve the issue, let me know.

[yizha1]

@Horiodino Great. I will assign this issue to you. You can check the link in the description. The problem is that the error was just passed through, instead, it should be captured by Ratify and create a new meaningful error message. /cc @susanshi @binbin-li for help in case you need support on the source code.