Exception details are lost when constructor with operation name is used.

When the exception is thrown with operation name the original errorMessage is lost.
For example

```
throw new CfnGeneralServiceException("Operation", new RuntimeException("something happend");
```

results in `"Error occurred during operation 'Operation'."` message.

If operation parameter would not be passed

```
throw new CfnGeneralServiceException(new RuntimeException("something happend")
```

then the message would contain `"something happend"`.

There are existing implementation's of resources that rethrow exceptions with operation field set, and the original message is thrown. What is more - if any exception will be unhandled explicitly `CfnInternalFailureException` will be thrown without errorMessage from the original exception and CloudFormation console will just display "Internal failure... " kind of message

首先追蹤 CfnGeneralServiceException 的建構函式，以及在例外未處理時建立 CfnInternalFailureException 的路徑。根據 issue 中的範例驗證操作名稱建構函式和內部失敗路徑；完成的標準是原始例外訊息在兩則 CloudFormation 錯誤訊息中都獲得保留。

由索引模型根據 Issue 內容生成。