The compute_transaction API endpoint response changed

[aaroncox]

Somewhere between 4.x and 5.x the way the /v1/chain/compute_transaction API endpoint changed how it responds when errors occur, which is causing it to be more difficult to use the endpoint to calculate resource requirements.

Previously it would allow the transaction to "process" and return any errors that occurred in the processed.except field with a nice error stack. If there was a tx_cpu_usage_exceeded exception, it would return the data alongside afield to easily access the stack[0].data.billed required for the transaction.

Now in post 5.x, it's throwing an actual 500 error as the response with more limited data as an error string, and no error stack.

What are the chances we can revert and go back to the previous behavior?